Privacy

Last updated 6 October 2026.

Your searches

We don’t keep the names you search or the descriptions you type. We never register, reserve, sell or share them, and we don’t use them to buy domains. Nobody at TLDMath watches searches to grab names.

What we store

What we share

To price a domain we send that domain name to registrar APIs (Porkbun, Namecheap, Dynadot, Cloudflare, Vercel, NameSilo, Name.com and Hostinger). To suggest names we send your project description to Anthropic’s Claude API. To look up a domain’s registrar and expiry date we query the public registry for that TLD (RDAP). To check handles we request the public profile URL for that name on GitHub, npm, PyPI, crates.io and YouTube. The launch kit, move plans and ownership cards look up the domain’s public DNS records through Cloudflare’s public resolver (1.1.1.1), and their live check loads the domain’s home page over HTTPS, as a visitor would. The AI visibility check reads the site’s public robots.txt, llms.txt and sitemap and loads its home page the same way; it stores none of it. Sign-in links and renewal reminders are sent through our email provider, Resend, which receives your email address for that purpose. We don’t send anything else about you.

TLDMath runs on Vercel (hosting, US) and Supabase (database, US), which process requests and the data above for us. Requests to Namecheap’s API go through a small relay server we run at Hetzner in Germany, which forwards the domain name to Namecheap. Like any web host, Vercel’s request logs record IP addresses and the web address requested for a limited time; for a normal search that address includes the name. When you click a buy or sign-up link you go to that company’s site, and its privacy policy applies there.

On your device

Your recent searches, your shortlist (the names you star), your “Describe my project” choices, your launch path (the domain you’re launching and which steps are done) and the setup steps you tick in the launch kit and move plan are kept in your browser’s local storage. They never leave your device as a list: opening the shortlist checks each name live, like a normal search, and we don’t keep the names.

If you arrive from a link that names a campaign (for example an ad), a cookie remembers that campaign name for 30 days so we can tell which campaigns are useful. It holds only the campaign name, nothing about you. If you sign in to Renewal watch, a cookie keeps you signed in.

Page views

We count page views with Vercel Web Analytics, which sets no cookies and doesn’t identify you. It receives the page you opened with everything after the “?” removed except a campaign tag (so never a searched name or a sign-in token), the site you came from, and your browser, device type and country.

MCP connector and Agent Skill

The connector is read-only. It receives only the tool arguments your AI client sends (a domain, name or TLD, a project description, a list of domains, a host and email choice, and for a move plan package and environment-variable names, never values) and handles them as described above.

The tldmath-launch Agent Skill is a set of instructions that runs inside your own AI tool. It asks TLDMath for the same read-only plans. Any change it makes to your DNS, hosting or email runs on your computer with your own logins and keys, which are never sent to TLDMath.

Contact

TLDMath is operated by Riverbend Crossroads Digital LLC. For questions or deletion requests, email support@tldmath.com.