Privacy
What naymme sends where: no accounts, no tracking, and exactly which third parties see your search.
naymme is designed to need almost nothing from you. There are no accounts, no sign-in, no cookies set by this app, no analytics or advertising trackers, and no client-side persistent storage — a search lives in the page's ?q= parameter and nowhere else.
What a search sends
When you run a check, your browser sends the candidate name to this site's API, and the server queries the relevant third-party sources on your behalf: RDAP and WHOIS servers and DNS for domains, the public endpoints of registries like npm, PyPI and crates.io, platforms like GitHub, and social networks. That means the name string itself — nothing else about you — is necessarily visible to those providers, exactly as if you had checked each site yourself.
Server-side handling
The API applies per-client rate limits keyed on the client IP address conveyed by standard proxy headers (cf-connecting-ip or x-forwarded-for); the key is used only to throttle abuse and is not persisted as an identity. The app is hosted on Vercel, whose infrastructure may keep standard request logs — see Vercel's privacy policy for that layer. No search results or names are stored server-side by this application.
What a result links to
Result rows link out to the providers themselves — registrar checkout pages, profile URLs, package pages. Following those links takes you to third-party sites with their own privacy practices, which this policy does not cover.
Changes
This policy describes the deployed site at naymme.vercel.app. If the data handling changes, this page changes with it. Questions about privacy are welcome via the contact page.