WhatsMyNameScope of this notice
This notice covers the username and email tools, optional Google connection, search history, and contact form. It describes the application’s current data flows and configuration. Production hosting, backups, and providers may have additional processing and retention that this application does not determine. Submit only identifiers you are entitled to research.
Where a query goes
| Activity | Data and destination | Site storage |
|---|---|---|
| Username scan | Username and site rules go to checker.whatsmyname.me; username and categories go to the configured apiv3/apiv4.whatsmyname.me scan services. | Query and results in history unless Privacy Mode is on. |
| Email scan | Email and categories go to the configured scan services, which return account-context signals. | Query and results in history unless Privacy Mode is on. |
| Public-web search | Query and country context go through our server to Serper (google.serper.dev) when available. | Seven-day result cache; history association when a history task exists. |
| Page visit | IP, request path, headers, and browser signals reach hosting infrastructure and loaded third-party resources. | Browser identifier; logs and provider records may also exist. |
What Privacy Mode changes
With Privacy Mode enabled, the browser skips creating and saving the scan’s history task. External scan and web-search requests still occur. It does not disable the browser identifier, analytics, advertising, provider logs, or the seven-day public-web cache. It does not erase earlier history or provide anonymity.
Cookies, URLs, and browser storage
A first-party identifier cookie links this browser to its user record and history. Its configured lifetime is 3,650 days, refreshed on requests; it is an identifier, not evidence of who operates the browser. An OAuth return cookie lasts one hour. Analytics may set their own cookies.
A query supplied in a URL can remain in the address bar, browser history, and request logs. Avoid sharing links containing sensitive identifiers. Pending-query session storage may be read and removed during restoration. Clearing site data removes browser-side identifiers; it does not delete database records.
Accounts and saved searches
A normal scan can create a guest user record containing language, country and browser-language metadata. Saved tasks contain the query, visitor IP, timestamps, result data, and available web context. History can be accessible in the same browser without a Google connection; protect shared devices.
Connecting Google associates its account ID, name, email and profile image with the user record. We do not receive your Google password. Logging out removes the site identifier cookie but does not delete saved records. Individual history deletion and Delete Account remove the corresponding active database records; account deletion also removes that user’s scan history.
Web search and AI
Public-web references use a search provider and may be unavailable in some countries. The application caches these results for seven days, including requests made in Privacy Mode. AI Search Results and AI Summary are currently disabled in the public interface. Any future activation that changes processing should be reflected in this notice.
External services and page resources
The shared page loads Google Analytics, Google AdSense, Tailwind/jQuery from jsDelivr, and Font Awesome from cdnjs. Result icons may use Google’s favicon service or a returned image URL. These requests expose ordinary connection and browser metadata; analytics and advertising can process page location and activity. Privacy Mode does not turn them off.
Scan-service internals, hosting locations, and provider retention are outside this application’s visibility. Opening a result or an external link sends a new request to that site under its own policy. Public information can still be sensitive when combined.
Google Dorks builds optional search links from the username or full email address you submit. Opening one sends that identifier and the selected search operators to Google in a new tab, where Google handles the search under its own policies. Privacy Mode still allows these outgoing searches. Copying a generated query places it on your clipboard when you choose the copy action.
Contact request records
The contact form stores your optional name, reply email, category, message, request reference, status, and timestamps in our database for handling and following up on the request. It does not send an automatic email. A hash derived from visitor IP and reply email is used in a 60-second submission limit.
Contact records are separate from search history and are not removed by Delete Account. Please omit passwords, tokens, payment details, and unnecessary personal data. Email correspondence is also subject to mailbox-provider processing.
Retention and deletion
The confirmed application expiries are seven days for public-web cache, one hour for the OAuth return cookie, 3,650 days for the refreshed browser identifier, and 60 seconds for the contact rate-limit entry. Cache expiry does not guarantee physical erasure of files or backups.
No automatic expiry is configured here for user, history, or contact database records. Infrastructure log rotation, backups, analytics settings, scan-service records, and support mailbox retention are not established by this codebase. We therefore do not promise a universal deletion deadline.
Your controls and requests
Input validation, history ownership checks, and request signing are implemented controls, not a security guarantee. Application and infrastructure logs may contain request metadata or error details; no production log or backup deletion schedule is asserted here. This notice will be revised when relevant processing changes.
- Review or delete individual scans in History. Use Delete Account to remove the current user and associated scan history from the active database. Logout and clearing cookies have different effects.
- Manage cookies and site storage in your browser and Google authorization through Google. Revoking Google access does not itself erase existing site records.
- For access, correction, deletion, or another privacy request, use the contact form or [email protected]. Applicable rights and exceptions depend on your circumstances; we may need enough information to locate the record and verify your entitlement.