Lookups and technical information
A lookup does not require an account. The service can store lookup events containing the searched number, a timestamp and a hashed IP identifier, together with operational information needed to provide results and limit abuse. Search and page activity may also be reflected in aggregate activity counts.
Web servers and infrastructure providers can keep access logs containing IP addresses, requested URLs, timestamps and browser information. A requested URL can include a phone number. We therefore do not describe lookups as unrecorded or completely anonymous.
Reports and votes
We store report text, submitted labels, phone numbers, dates, moderation information and technical identifiers used to prevent duplicate or abusive submissions. Approved report content can appear publicly. Optional or historical records may include IP or location information; hashing one identifier does not mean every stored record is anonymous.
Do not put private addresses, account information, passwords or another person’s sensitive details in a report. A report intended for publication is different from a private correction request.
Contact and correction requests
The contact form collects your email address, message, any name or phone number you supply, and security information used to process the request. These requests are stored in a private review queue. They are not published as community reports.
Use the correction and removal form to challenge displayed information or ask about data concerning you. Include only what is needed to identify the issue. The team may need more context before deciding what to change.
Analytics, advertising and abuse prevention
The site uses Google Analytics to understand traffic and Google advertising services to display ads. These services can process device and browser information, page activity and cookies. Number-page URLs may reveal which number page was visited. Google reCAPTCHA is used to help prevent automated abuse.
Google explains its processing in its privacy policy and its information about partner sites and apps. Browser settings and the controls offered by Google may let you manage cookies and advertising preferences. Blocking these services can affect some site functions.
Sources and service providers
Phone information may be retrieved from existing records or an upstream service, including WhoseNo. A lookup can require sending the searched number to that service. Source labels and dates should be read alongside each result; a contact-derived label is not a verified carrier identity. Read our data methodology.
Hosting, database, analytics, advertising and abuse-prevention providers may process information while delivering their services. Their own policies also apply where you use their services directly.
Retention and requests
Lookup events, reports and requests can remain stored for service operation, abuse prevention, moderation and handling disputes. Technical logs and third-party services have their own retention settings. This policy does not promise that all records are deleted after a fixed number of days or immediately when a session ends.
You can contact RevealNames to ask about access, correction or deletion. Removing public content and deleting every technical or backup record are different actions; specify what you are requesting. Avoid sending identity documents in the first message.
Use of the service
The site is not intended for children to submit personal information. If you believe a child has submitted personal information, use the private form to request review.
Updates to this page are dated above. See the terms of service for restrictions on using lookup results.