WhatsMyNameAppWhat this notice covers.
This notice applies to whatsmynameapp.net and its username and email research tools, optional Google account connection, saved search history, public pages, and support form. “WhatsMyName App,” “we,” “us,” and “our” refer to the operator of this service.
The descriptions below reflect the current application's data flows. Hosting, analytics, advertising, scan providers, and external sites also process requests under their own settings and policies. This notice does not promise a particular retention period for provider systems, infrastructure logs, or backups that the application does not control.
Submit only an identifier you have a legitimate basis to investigate. Search terms can relate to a person. The tools do not need passwords, private mailbox contents, or unrelated sensitive records.
Where information goes.
Swipe to read the full table
| Activity | Information involved | Processing and storage |
|---|---|---|
| Visit a page | Connection IP, requested URL, headers, browser/device information, cookies. | Our hosting infrastructure, enabled analytics and advertising services, and asset hosts can receive ordinary request information. |
| Run a scan | Username or email, category, page, and returned source data. | The scan service receives the query in both modes. Standard mode also creates a first-party task and can save positive matches. |
| View source icons | The origin of a valid result URL and normal connection information. | The browser can request icons directly from Google's favicon service. |
| Connect Google | Google subject ID, name, profile email, profile-image URL. | Basic profile fields are stored with the user record. We do not receive the password entered with Google. |
| Contact support | Optional name, reply email, category, message. | A separate contact-request record contains these fields, a reference number, status, and timestamps. |
Privacy mode has a specific scope.
Standard scans
Before a standard scan, the browser sends the validated identifier to this site's task endpoint. A visitor record can be created if needed, and the task stores the query, type, task identifier, completion state, IP, and timestamps. Positive matches can then be normalized and saved against that task.
The browser also sends the identifier, selected category, page, and request-signing information to a configured scan service. Username checks can use up to 4 concurrent category lanes; email categories run sequentially. Every returned row can appear in the live response log, while positive matches form the saved result set.
Scans with Privacy mode enabled
Privacy mode is off by default. Enable it before starting a scan to skip first-party task creation, result saving, and task completion for that run. The switch is locked while the scan runs.
The configured scan service still receives the submitted identifier and the information required to perform its checks. Privacy mode does not disable normal page traffic, cookies, analytics, advertising, provider processing, or browser history. Scan requests use URLs, and identifiers included in a page or request URL may also be processed by browser, server, or provider systems.
See About & method for the scan flow, status rules, progress calculation, and source limitations.
Saved searches can exist without Google login.
A database visitor record may be created when a valid standard scan starts. It can contain the browser identifier, nickname, language, country information supplied by the infrastructure, a shortened language header, and timestamps. Standard history records hold the query, normalized positive results, simplified site names, IP, and task metadata.
Negative, unknown, skipped, and error responses stay in the live log rather than becoming saved positive matches. Live category counts, full page logs, and progress indicators are not preserved as separate history fields. Older saved records may contain information from earlier versions of the service.
Anyone using the same browser profile may be able to view its linked history. Optional Google login requests the openid, email, and profile scopes. The returned Google ID, name, email address, and avatar URL can be stored in the user record. Google handles the password entry and applies its own policies.
A separate record for each conversation.
The contact form sends the optional name, reply email, selected category, and message to this site. The application stores them with a public reference number, review status, and creation/update times. A successful submission means the request has been stored; it does not promise an immediate reply.
To reduce repeated submissions, the application hashes the connection IP together with the lowercased reply email and caches that rate-limit key for 60 seconds after a successful submission. The form does not write the raw IP or that key into the contact-message table. Ordinary infrastructure logs can still process request information.
Support records are separate from search accounts and are not automatically removed by account deletion. Quote the reference number when requesting review, correction, or deletion of support correspondence. If you contact us by email, your mail provider and our support-mail systems also process that communication.
The browser also connects to other services.
- Hosting and network infrastructure. The web server, network providers, and Cloudflare where used can process IPs, headers, URLs, and operational logs. Country/location headers may be available to the application; these are connection-derived estimates.
- Scan services and source platforms. A configured scan endpoint receives the identifier and check parameters. The sources it checks control their own response behavior. Opening an external result creates a separate browser request to that site.
- Google Analytics and advertising. The shared layout loads Google Analytics and Google AdSense scripts. These may process page URLs, browser/device information, identifiers, cookies, and interactions under Google's policies and the relevant account/browser settings. We do not promise that enabling Privacy mode disables them.
- Google OAuth and favicons. Optional login exchanges basic profile data. When result icons are displayed, Google can receive the requested site's origin and ordinary connection information, even when the icon request omits a referrer.
- Asset CDNs. Tailwind CSS and jQuery are loaded through jsDelivr, and Font Awesome assets through cdnjs. Those hosts receive the normal information accompanying resource requests.
Third-party processing locations and retention depend on their own systems and policies. The current scan interface does not add AI-generated summaries or indexed web-search results.
Deletion controls, with clear boundaries.
No fixed automatic expiry is defined in the current application for user, search-history, or contact-request rows. Saved data can remain until you delete it or the operator removes it. Contact records are kept to receive, review, and follow up on requests; this notice does not promise a fixed automatic purge schedule.
Self-service deletion removes the selected history task, or the current user record and all linked history, from the active application database. It does not establish when a separate support record, provider copy, infrastructure log, or backup is erased. Cache expiry is also not proof of deletion from every related system.
The application uses input validation, browser/account-scoped history operations, and signed scan requests. These reduce some risks but cannot guarantee that the site, your browser, or a provider is free from compromise. Protect access to the browser profile, connected account, and any results you choose to export or share.
Review, remove, or ask us about a record.
- Enable Privacy mode before a scan to keep it out of this application's saved history.
- Use the account menu to review username or email history and permanently delete individual tasks.
- Delete the current account and all linked search history from the sidebar. These actions have no self-service undo.
- Clear browser cookies/session storage or sign out, understanding that those steps alone do not delete database records.
- Manage Google authorization and analytics/advertising preferences through Google and your browser. Revoking authorization does not itself erase profile fields already stored here.
- For access, correction, deletion, or other data requests available under applicable law, contact us with enough information to locate the record. We may need to verify that you are entitled to control it.
Removing data here cannot remove a public profile or information held by an external platform. Contact the original source for changes to its records.
Questions and future changes.
We may update this notice when the product, its data flows, or its providers change. The revision date appears above. For questions or requests, use the contact form or email [email protected]. Include only the information necessary to understand your request.