Privacy Policy

Last updated: October 14, 2026

Introduction

This policy describes what Namester.ai ("we", "Namester") collects when you use namester.ai, why, which other services receive it, and how to contact us about it. It describes how the site works as of the date above. If that changes, we will update this page and the date.

What we collect

If you only browse

You can search, filter and open domain pages without an account.

• Analytics. Page analytics are provided by umidata.com, a separate analytics service that runs the open-source analytics tool Umami. It does not set cookies, and our page code tells it to send nothing when your browser has Do Not Track turned on. For each page view it records the page address — including anything in the address, such as the words you searched for — the referring page, your browser, operating system and device type, and an approximate location derived from your IP address.
• Outbound links. When you follow a link from our site through our redirect — to a marketplace, or to an outside lookup page for a domain (WHOIS, DNS, a Google search or the Wayback Machine) — we record the domain name, the marketplace (for marketplace links), the kind of link and the time. We do not record your IP address or account with it.
• Rate limits. To enforce usage limits we keep counters keyed by your IP address (or your account, when you are signed in) in a database on our own server. Counters expire shortly after their limit window ends; for AI search the window is one day (UTC) when you are not signed in or use a free account, and one hour on a paid plan.
• Technical logs. Our servers keep technical logs, such as errors and counts of AI-search usage, to run and debug the service.

AI search (Discover)

When you type a sentence on the Discover page, we send that sentence to a third-party AI model through OpenRouter, which currently routes it to a Google Gemini model. The model turns it into ordinary search filters, which we show on the page. We keep the parsed result in our server's memory for up to 10 minutes so that repeating the same search does not call the model again. The sentence also appears in the page address, so it is included in the analytics described above. Please don't type personal information into the search box.

If you create an account

You sign in with a link sent to your email address or, where a "Continue with Google" button is shown, with your Google account; there is no password.

• Account data: your email address, when you signed up and last signed in, and the site language you last used while signed in. For each signed-in session, the sign-in service also stores the IP address and browser (user agent) it was started from, and it keeps a log of sign-in events.
• If you sign in with Google: Google tells us your email address and whether Google has verified it, your name, the address of your profile picture, an identifier for your Google account and, for Google Workspace accounts, the domain the account belongs to. The sign-in service stores these with your account. When you sign in on Google's own page, Google also issues an access token that can only read this basic profile; the sign-in service holds it briefly while it completes your sign-in, and it may stay in your browser's sign-in cookie, together with your session, until the session is next refreshed. We do not use that token, and we do not read any other Google data.
• Things you save: watchlist entries and the notes you add to them, saved searches (the filters, their name, and their alert settings), your notification preferences, and API keys. API keys are stored as hashes; we keep only a short prefix so you can tell them apart, and when each key was last used (to within about five minutes).
• Email alerts: a record of which notification emails we sent you, and — for saved-search alerts — when you confirmed or unsubscribed an address.

AI Screening

AI Screening applies questions you write to a list of domain names. For each name in a run, we send your questions, the name and a snapshot of the listing data we hold for it (such as its length, extension, marketplace, auction end time and number of bids — no prices, and nothing about you or your account) through OpenRouter to an AI model from Google, Anthropic or OpenAI, depending on the model class you choose. OpenRouter may run a model through its maker or through a cloud platform that hosts it (currently Google Cloud, Microsoft Azure or Amazon Web Services). We ask OpenRouter to send these requests only to provider endpoints that, under OpenRouter's provider policies, do not store or train on the data. Please don't put personal information in your questions.

If you attach a screening to one of your saved searches, it runs the same way on that search's new matches whenever its alert is due, and the alert email lists the names that passed.

We store your saved screenings (their names and questions) and which saved search each one is attached to; each run, with the questions it used, where its names came from, its progress and the AI points it used; each result, with the data snapshot that was sent to the model; for each screened saved-search alert, the names that were sent and the question that decided which passed; and a ledger of the AI points each run and each name used. Results are shown only to you.

How we use it

• To run the site: sign-in, your watchlist, saved searches, API keys and usage limits.
• To send the emails you asked for or that come with your account settings: sign-in links, alerts when a watched auction is about to end or its price changes, a daily digest, and saved-search alerts after you confirm them. Watchlist alerts and the daily digest are on by default for new accounts; you can turn each of them off in your notification settings. These emails are written in the language you last used the site in while signed in (for a new account, the language of the page where you created it). Until we know it, sign-in emails show English, Chinese and Japanese side by side, saved-search alerts use the language of the page where you saved the search, and other emails are in English.
• To understand how the site is used and fix problems.

We do not sell your personal information, and we do not use advertising or marketing cookies.

Paid plans and access grants

When you start or manage a paid plan, we send Stripe your email address, an internal account identifier, and the selected plan. Payment details are entered on Stripe-hosted pages. We store Stripe customer, subscription and invoice identifiers, amounts, currency, payment status and billing dates to fulfill and manage access. Administrator access grants store the plan, authorization reason and access dates; a grant is not a payment.

Who else receives data

• Stripe processes paid subscriptions and billing management. It receives the account and payment-page information described above; its processing is also covered by Stripe's privacy policy.

• Google provides "Sign in with Google". If you use it, you sign in on Google's own page or prompt. Separately, while you are signed out, the home page and the sign-in page may show Google's sign-in prompt, which makes your browser load Google's sign-in script from accounts.google.com. In both cases Google receives your IP address, browser information and the address of our site; its processing is covered by Google's privacy policy.

• Cloudflare Email Service sends our emails. It receives your email address and the content of each email.

• OpenRouter and the model provider it routes to (currently Google) receive the sentences you type on the Discover page, as described above.

• umidata.com receives the page-view data described under "Analytics" above.

• UptimeRobot regularly requests a public health-check address on our site to tell us when the site is down. It receives no data about you.

• OpenRouter and the AI model providers it routes AI Screening requests to — Google, Anthropic and OpenAI, or a cloud platform hosting their models (Google Cloud, Microsoft Azure or Amazon Web Services) — receive the questions, domain names and listing data described under "AI Screening" above.

Our database, sign-in service (the open-source Supabase software) and rate-limit counters run on servers we operate ourselves; they are not hosted by those projects' companies.

Some of these providers process data outside your country.

Backups and how long we keep data

• Account data is kept until you ask us to delete your account.
• Daily database backups, which contain account data, are kept on our server for about 14 days, and a copy of the server's files is kept on separate backup storage for about 14 days.
• AI-search results stay in server memory for up to 10 minutes. How long OpenRouter and Google keep a request is governed by their own policies.
• Analytics data is kept by umidata.com. We do not yet promise any deletion date for it.
• Outbound-link records do not identify you and do not yet have a set deletion date.
• AI Screening runs and their results, including the data snapshots, are deleted 90 days after the run ends. Records of screened saved-search alerts are deleted 90 days after the alert was prepared. Screenings you delete leave your list right away and are erased 90 days later. The AI-points ledger is kept with your account until you ask us to delete the account. How long OpenRouter and the model providers keep a request is governed by their own policies.

Cookies and browser storage

• NAMESTER_LOCALE is set only when you choose a language with the language switcher or a language link in the footer, and remembers that choice for one year. Until you choose one, every visit uses your browser's language preference; nothing is stored for that. (Earlier versions of the site could set a session cookie named NEXT_LOCALE holding the language of the last page you visited; it is no longer set or read.)
• langAlertDismissed is set for 30 days only if you dismiss the language suggestion banner.
• When you are signed in, the sign-in service sets session cookies that keep you signed in.
• When Google's sign-in prompt is shown, Google's script may set a cookie named g_state on this site that records the state of the prompt (for example, that you closed it, so it stays hidden for a while). The prompt and the Google sign-in page themselves are served by Google and may use Google's own cookies on Google's domains. We do not read either.
• Your browser's local storage keeps your light/dark theme choice, and its session storage keeps your place in paginated tables.

There are no advertising, marketing or third-party analytics cookies. You can clear cookies and storage in your browser at any time; if you do, you will be signed out.

Your choices and rights

You can change or turn off notification emails in your account's notification settings, and remove saved searches and watchlist entries yourself. To get a copy of your data, correct it, or have your account and its data deleted, email hi@namester.ai from the address on your account. We handle these requests by hand. Depending on where you live, you may have further rights under your local law.

Children

Namester.ai is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.

Changes to this policy

When how the site handles data changes, we update this page and the date at the top.

Contact

Questions about this policy or your data: hi@namester.ai.