Privacy Policy

1. Who is responsible

The company identified at the top of this page is the data controller for the information described here. Write to the contact address listed there with any privacy question or request.

2. What we collect

• Account data: your email address, your name if you provide one, the sign-in method you used, and the persona and preferences you choose during setup.
• Plan and billing data: your plan, your credit balance and its history, and the payment records Stripe returns to us. We never receive your full card number.
• Product data: the searches, saved searches, Radars, watchlists and notes you create.
• Usage data: the pages you open, the actions you take, your IP address, your browser and device, and the referring page.
• API data: the calls made to our public API and its connector, as section 8 describes.
• Support data: the messages you send us through the chat widget or by email.

3. Analytics, chat and measurement

We want to be specific here, because some of this is more detailed than visitors expect. When you open the public website, these load automatically:

• Google Analytics 4, which records page views and events and sets cookies to recognise a returning browser.
• Mixpanel, which records product events automatically and captures session recordings of your visit, including the pages you view and the way you move through them.
• Crisp, our support chat, which sets cookies so a conversation continues across pages.
• The Brevo tracker, which records the pages you view and sets a cookie so we can tell whether an email we sent you led to a visit. If you are signed in, your email address is sent to Brevo so the visit is attached to your contact record.

We use this to understand which pages work, where people get stuck, and which changes help. We do not sell it, and we do not use it for advertising.

We are adding a consent control so you can refuse analytics and session recording before they load. Until it ships, you can block them with your browser privacy settings, a tracker blocker, or by writing to us and asking us to delete what we hold about your visits.

4. Cookies

• Necessary cookies keep you signed in and carry a request identifier we use to trace errors. The site does not work without them.
• Attribution cookies record how you found us, so the account you create carries it. A cookie named r holds a referral code, and cookies named utm_medium, utm_source, utm_content, utm_campaign, utm_product and utm_feature hold the campaign tags of the link you followed or, when the link had none, the address of the page that sent you. Each is written once and never changed. A cookie named utm_cta adds each of our buttons you follow on the way to sign up. They are read when you create an account and expire after 30 days.
• Analytics cookies are set by Google Analytics, Mixpanel and Brevo, as described above.
• Support cookies are set by Crisp so your chat history follows you between pages.

You can clear or block cookies in your browser at any time. Blocking necessary cookies will sign you out.

5. Why we are allowed to process it

• To perform our contract with you: your account, your plan, your billing and the features you use.
• To meet a legal obligation: keeping accounting and tax records.
• For our legitimate interest: keeping the service secure, preventing abuse, and understanding how the product is used.
• With your consent: marketing emails, which you can stop from the footer of any email we send.

6. Who processes data for us

• Stripe, for payments and subscription management.
• Brevo, for transactional email, the newsletter, alert delivery, and our internal error reports. Those reports can include your account email, your IP address, and the request that failed.
• Google Analytics, for website measurement.
• Mixpanel, for product analytics and session recording.
• DeBounce, which checks at signup whether your email address can receive mail.
• Discord, where we receive internal notifications about new accounts and payments. They include your account email.
• Crisp, for support chat.
• OpenFreeMap, for the map on the agenda and calendar pages. When you open the map, your browser loads it from tiles.openfreemap.org, which receives your IP address.
• Instatus, for the status badge on the API page. When you open that page, your browser loads the badge from uniquedomains.instatus.com, which receives your IP address.
• Anthropic, for generating the editorial content published in Domaining News, and for checking the words sent to our API’s word intake (section 8). Neither use includes your personal data.
• Our hosting and database providers, which store the data described here.

7. How long we keep it

• Account and product data: for as long as your account exists. When you ask us to delete your account, we erase it from our database and from our email, analytics and payment processors in one go.
• Billing records: for the period our accounting and tax obligations require. Stripe keeps the invoices and payment records of a deleted account for that reason.
• Internal notifications we have already received about your account, by email or in Discord, cannot be recalled after deletion.
• Usage and analytics data: according to the retention set in each analytics tool, and no longer than needed to understand product usage.
• Support conversations: for as long as they are useful to answer follow-up questions.
• API request log: 12 months. Once a month, we delete the lines older than that (section 8).

8. The API and the connector

This section covers the public API at https://api.unique.domains/v1 and the connector, our MCP server, which AI assistants such as Claude and ChatGPT reach at https://mcp.unique.domains/mcp. The free answers and every connector answer come from the dataset we build and store ourselves: domain names, endings, registrar prices and market figures. A name’s registry answer repeats the public record the registry of its ending publishes, which can include the name or the organization of the person who holds the name when the registry shows it.

Three calls that need a key ask someone else, and send them the name or word alone, never anything about you: a live check looks the name up in the public DNS and asks, through our proxy provider, the registry of the name’s ending and registrars whether the name is taken; an appraisal asks our appraisal model provider for a value; a word intake asks our AI provider, Anthropic, whether the word fits our catalog. A word we accept joins our catalog and is then looked up like every other word in it: by our AI provider, in public reference and search-data sources, and as names at registries and registrars.

• The request: the path of each call, which includes the name or word you ask about, with its time, its answer’s status and how long it took. For a refused call, the refusal’s code and message, which can repeat the name, the word or another value you sent. We keep one line per call in our request log, and never log the query string or the body of a call.
• Your IP address, to apply the free limit of 60 calls an hour and 100 a day from one address and the lookups limited to one a day. It stays in the server’s memory beside the counts of the current hour and day, is never written to our request log or any table of ours, and is dropped when newer addresses take its place or the server restarts. The hosting providers of section 6 see it at their edge and can keep it in their logs, and an error report (section 6) can include it.
• With a member key: your account and the key’s prefix on each line of the request log, and the month’s counts of calls, live checks, appraisals and word intakes on your account. We store the key itself only as a hash, with its prefix and when it was made and last used; a revoked key keeps its hash and prefix until your account is deleted.
• With a RapidAPI subscription: the user id RapidAPI sends with each call and your subscription’s tier.
• A word intake: the word you ask us to add, kept with the request so we can answer it, with your RapidAPI user id or, with a member key, a code made from your account that counts your requests of the day.
• Through the connector: nothing that identifies you or your conversation. Your assistant sends the connector a tool call, which holds the name or word asked about; the connector makes the API call under its own name, and the request log records one call from the connector with that path. The connector keeps no record of the calls it passes on. When your assistant or editor runs on your own machine, as Claude Code, Cursor and VS Code do, it connects to the connector from your IP address, which the hosting providers of section 6 see like any other call.

We use this to answer the call, to apply the free limits, the daily caps on live checks and word intakes and a plan’s monthly allowance, to let RapidAPI bill its subscribers, to find abuse and errors, and for our internal reports of usage and costs. We do not use it for advertising and we do not sell it.

RapidAPI receives the calls of its own subscribers, because those calls pass through RapidAPI, and its privacy policy covers them. Apart from RapidAPI, the processors of section 6 and the name or word the three calls above send, we send API and connector data to nobody.

• We keep each line of the request log for 12 months: once a month, we delete the lines older than that. When your account is deleted, your keys, their monthly counts and every line of the request log made with your keys are deleted with it. The words you asked us to add stay with us, with nothing that links them to you.
• You can revoke your key at any time in Settings, Account, API: it stops working at once.
• The connector needs no account and stores nothing about you, so there is nothing of yours to delete there. For any other request about API data, write to the contact address at the top of this page.

9. Transfers outside the EU

Some of the processors listed above are based outside the European Union. Where that is the case, the transfer relies on the European Commission standard contractual clauses or on an adequacy decision.

10. Your rights

If you are in the European Union or the United Kingdom you can ask us to give you a copy of your data, correct it, delete it, restrict how we use it, or object to our use of it. You can also ask for your data in a portable format.

Write to the contact address at the top of this page. We answer within one month. If you are not satisfied, you can complain to the data protection authority in the country where you live.

11. Children

The service is for people aged 18 and over. We do not knowingly collect data about children.

12. Changes to this page

When we change how we handle data, we update this page and change the review date shown at the top. If a change is significant, we tell account holders by email.