Effective October 20, 2026
Privacy Policy
This policy explains how information is handled when you use Namestake. The service works without an account.
Information you provide
When you run a check, we process the name, selected industry and region, and any domain or social-handle variation you enter. Opening a result or shared-set link can also start checks for its name. Only submit information you intend to send to the services needed for these checks.
Information collected automatically
Our hosting provider may process ordinary technical information such as an IP address, request time, device or browser details, and error logs to deliver and secure the service. Namestake also uses a daily rotating, one-way representation of an IP address to enforce usage limits; the raw address is not stored in Namestake’s rate-limit table.
How information is used
We use this information to return name-viability results, generate requested AI-assisted observations, prevent abuse, diagnose failures, maintain security, and improve the reliability of the service. We do not sell personal information or use submitted names for advertising.
Service providers and public sources
Cloudflare provides hosting and supporting infrastructure. OpenAI processes requests for AI-assisted observations. Domain checks use Fastly’s Domain Management service (Domainr) and may fall back to public registration services. Checks may also contact social platforms, dictionary sources, and the public USPTO trademark search through Cloudflare’s hosted browser. Relevant names, domains, handles, or selected context are sent as needed for those requests. External links take you to third-party services with their own terms and privacy policies.
Search privacy and retention
Ordinary searches do not put the name or description in the page URL. Share links contain the information you choose to share. New search results are not written to Namestake’s server response cache. Temporary request data is used while checks run, and anonymous usage-limit and service-cooldown records are retained to operate the service. Search results remain in the open browser page; saved sets stay in browser storage only when you press Save. Older cached records require a separate cleanup during deployment. Hosting and external check providers may retain request data under their own settings and policies; disabling AI response storage does not by itself guarantee zero provider retention. We do not promise that a name sent for checking is never disclosed to a service provider.
Cookies and saved sets
Namestake does not use advertising cookies or require an account. Essential hosting or security technology may still be used. Saved sets are stored in your browser’s local storage, including the name, selected domain and handle, platform, category, and region. When a check is complete, the saved copy may also include its checked date, displayed verdict, inferred trademark classes, and summary signal statuses. Starting another search does not automatically save the previous set. These saves are not account-synced and remain until you remove them from Shortlist or clear browser data. Clear set resets your current selection; it does not remove saved copies. Use Remove in Shortlist to delete one saved set, or clear Namestake’s site data in your browser settings to delete all of them.
Shared links
A shared screening record contains the name, context, region, check time, verdict, summary, source links and selected addresses in the link’s fragment (the part after #). Opening a shared screening record does not rerun checks, and its fragment is not sent to Namestake’s server. Links shared from Shortlist contain the saved name, context, region, and selections in URL parameters and start a fresh check when opened; they do not include a saved verdict. They are not encrypted or protected by sign-in: anyone with the link can read them. URLs may appear in browser history, hosting logs, link previews, or services where you share them. Clearing or changing your set does not revoke copies of a shared link. Share only information you intend recipients to see.
Your choices
You can avoid sending a name to the service by not running a check. You can also verify sources manually using the provided links. Browser controls may be used to limit cookies or stored site data, although doing so can affect future functionality.
Children’s privacy
Namestake is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
Contact
For privacy questions or requests, email ryanleescott@gmail.com.
Changes to this policy
We may update this policy as Namestake evolves. The effective date above will change when we do, and material changes will be reflected here.