Privacy Policy

Who is responsible

[OPERATOR NAME], [OPERATOR ADDRESS], is the controller of the personal data described here. Contact: [contact email] or the contact page.

What you can do without an account

Searching, browsing lists, TLD pages, analytics and the domain check work without an account. We do not ask for your name or email for that. Your requests still reach our servers, so your IP address is handled as described under "IP addresses and rate limits" below.

Account data

When you sign up with an email address and password we store your email address, your password as a salted PBKDF2-SHA256 hash (never the password itself), your plan and the time you registered. When you sign in with Google we receive your Google email address (which Google must have verified) and Google's account identifier; we store both, linked to your account, and we do not store your Google name or picture. A Google sign-in for an address that already has a TLDlive account links to it.

We use this data to run your account, to log you in, to enforce plan limits and to contact you about the service.

Cookies and local storage

• di_session: your login session. HttpOnly, Secure, SameSite=Lax, valid for 30 days. The server keeps only a keyed hash of its value, together with your account id and expiry. Removed when you log out.
• tl_in: a flag with the value 1 that tells the page whether to ask the server who you are. It holds no identity or secret and lasts 30 days.
• g_state: a short-lived (10 minutes) cookie that protects the Google sign-in flow against forgery. Only set while you sign in with Google.
• Local storage in your browser: your light or dark theme choice, and a short-lived note of the action you were about to take (for example watching a domain) so it can finish after you sign up or log in. It never leaves your browser.

These are strictly necessary for the features you use, and we do not use advertising or cross-site tracking cookies. Cloudflare Turnstile, our bot check on sign-up and after repeated failed logins, may run a challenge in your browser; it is provided by Cloudflare under its own privacy terms.

Email we send you

We send an address verification link when you sign up with a password (valid 24 hours, single use), a notice if someone signs up with an address that already has an account, and, if you create watches, a digest of matches. Every digest has an unsubscribe link. These emails are sent through Cloudflare's email sending service. We do not send marketing email.

Your watches (the keywords or domains and TLDs you chose) and their matches are stored in your account. Delivered matches are deleted after 90 days, and deleting a watch deletes its matches. We keep a log of when digests were sent, how many matches they held and whether sending succeeded.

API keys

When you create an API key we store only a hash of it, its prefix, the name you gave it, when it was created, when it was last used and whether it was revoked. The full key is shown once. We count the calls made with each key per UTC day to enforce your plan's quota.

AI assistant (chat)

When you use "Ask AI", the messages you type in that conversation are sent to Anthropic (the Claude API) so that it can answer, together with our instructions and the results of the data lookups it requests from TLDlive. We do not send your email address or account details. We do not store the text of your conversations on our servers: the conversation lives in your browser page and is lost when you leave. We record usage figures (your plan, token counts and cost) without message text. Anthropic processes the messages under its own terms and privacy policy; please do not put personal or confidential information into the chat. Chat use is limited per day by user or IP address.

Payments

Paid plans are sold through Polar (polar.sh). You enter your card and billing details on Polar's pages, not ours, and Polar handles taxes and its own records under its privacy policy. We receive and store the subscription and customer identifiers, the plan, the subscription status, the end of the current period and whether it is set to cancel, so that your plan matches what you paid for. If you only register interest in a plan we keep a record of that against your account.

Analytics

When it is switched on, we use Cloudflare Web Analytics, a cookieless service, to see aggregate traffic such as page views and performance. It does not use cookies or track you across sites, and we get totals, not profiles of individual visitors. If it is not switched on, no analytics script is loaded. Cloudflare also processes the requests to our site as our hosting and security provider (see below).

IP addresses and rate limits

To keep the service available and fair we count requests per IP address (or per account or API key when you are logged in). Those counters live in Cloudflare's rate-limiting, Durable Object and key-value stores and expire automatically, within about two days. We cap the number of new accounts per IP address per day, and count failed logins per IP address and per email address (stored as a hash) for 10 to 15 minutes. We do not store IP addresses in your account record. Cloudflare, which hosts the site, sees IP addresses and keeps request and error logs for a limited period under its own terms.

TLDlive Lens

The optional browser extension has a separate policy that explains exactly what it does locally and what, if anything, it shares when you opt in: see the Lens privacy policy.

Domain and zone data

The domain lists and statistics come from registry zone files obtained through ICANN's Centralized Zone Data Service and from public RDAP and DNS lookups. This data is about domain names and their name servers, not about our users, and a zone file contains no registrant details. If a domain name itself identifies you and you want something corrected, contact us.

Who else handles data

We use these providers to run TLDlive: Cloudflare (hosting, the D1 database that stores accounts, caching, email sending, bot protection and analytics), Google (only if you choose Google sign-in), Polar (payments), Anthropic (AI assistant), and ClickHouse (a database service that holds the zone and analytics data). Account data is stored in Cloudflare's network. Some of these providers are outside your country, so your data may be processed abroad. We do not sell your data and we do not share it for advertising.

How long we keep data

• Account data: until your account is deleted.
• Login sessions: 30 days; expired sessions are deleted by a scheduled job.
• Email verification links: valid 24 hours; expired or used ones are deleted after a further 7 days.
• Delivered alert matches: 90 days. Watches: until you delete them or your account.
• Rate-limit counters: about two days.
• Billing records: the subscription identifiers and status for as long as your account exists, and as long as the law requires for accounting records held by Polar.

Your choices and rights

You can delete watches and revoke API keys yourself, unsubscribe from alert emails with the link in each email, and log out to end a session. Depending on where you live you may have the right to access, correct, export or delete your personal data, to object to or restrict processing, and to complain to your data protection authority. You can delete your account yourself on the Account page (Delete account, at the bottom): it asks you to confirm, and to enter your password or, if you signed up with Google, to have logged in within the last 10 minutes. Deletion immediately and permanently removes your account, login sessions, watches and their matches, alert delivery log, API keys, plan interest and email verification records. An active paid subscription must be cancelled first from the billing portal. To exercise any other right, or if you cannot use the page, write to [contact email] from the email address on the account and we will respond within a reasonable time, normally within 30 days.

Children

TLDlive is not directed at children under 16 and you must be at least 16 to create an account.

Security

Passwords are hashed with a salt, sessions and API keys are stored only as hashes, traffic uses HTTPS, and access to our databases is restricted. No system is perfectly secure; tell us at once if you suspect a problem.

Changes

We may update this policy. The date at the top shows the latest version, and for material changes we will give notice on the site or by email. See also the Terms of Service.