Last updated: 2026-11-21
NameFactors (https://namefactors.com) is operated by Syrenox Systems Ltd, a company registered in Israel (company number 517155438). This policy explains what information we collect, why, who else receives it, how long we keep it, and what you can ask us to do with it.
1. In short
- NameFactors tests candidate names. To test a name, we send it to the companies that run the tests: speech-recognition and AI-model providers, and a domain-availability provider. We send the name, and nothing about you.
- Your candidate lists, projects and results are private to your workspace. We do not disclose other customers' candidate lists, testing activity or decisions, and we design the product so that one customer's work is not observable by another.
- We keep a name's test results after your project is deleted, with no link to you, your workspace or your project, and reuse them when anyone tests the same name. We may count them in aggregate statistics that never expose a name or who tested it.
- We use no analytics, advertising or tracking. One cookie keeps you signed in.
- We never see your card. Credit packs are sold by Creem, the merchant of record.
- Our servers and database are in Frankfurt, Germany. Backups are encrypted and stored in the EU.
2. What we collect
2.1 Your account
- Your email address, which identifies your account.
- Your name and profile picture, if you sign in with Google or set a name yourself.
- Your password, if you set one. We store a hash of it, never the password itself.
- When we last had evidence that you control your email address, and how (Google, or a code we sent you).
- Whether and when you were admitted to the product, and by what route. NameFactors is in a private beta; creating an account does not by itself grant access.
- Your display preferences for the app's screens.
- Which version of the Terms of Service and of this policy you agreed to when you created your account, and when.
Google sign-in. If you sign in with Google, Google sends us your name, email address and profile picture, confirmation that your address is verified, and an identifier for your Google account. They become your account's details and are used as those are: to sign you in, to email you about your account and your workspaces, and to show your name and email address to the other members of workspaces you share. An invitation you send shows your email address to the person you invite. We keep this information with your account and delete it as §7 describes, including from backups. We ask Google for nothing beyond signing you in, and keep no Google access tokens. We do not sell this information or use it for advertising; §4 describes who else receives it. Our use of information received from Google APIs adheres to the Google API Services User Data Policy.
2.2 Signing in and keeping your account safe
- Sessions. Each signed-in session records when it started and was last used, your browser's identification string, and your IP address in two reduced forms: a hash, to recognise the same address again, and a truncated prefix, to show you where a session came from. The full address is not stored with the session.
- Security records of sign-ins, failed sign-ins and the use of connected AI assistants, with the same reduced IP forms and your browser's identification string.
- Sign-in codes sent to your email for sign-up and password reset. We store a hash of the code, valid for 15 minutes.
- Rate-limiting records, so that nobody can guess passwords or codes or flood an inbox. They are keyed by your email address or IP address and deleted when the limit's window passes.
- Server logs, which include IP addresses and are kept for a short time by our hosting provider. Logs refer to records by their identifiers, not by names or project content. When a sign-in code cannot be delivered, the log records the address it was meant for.
2.3 Your workspace
A workspace is where projects live and credits are spent. For each workspace we keep:
- its name, its members and their roles;
- invitations you send: the invitee's email address, the role offered and any message you write;
- its credit ledger: every grant, purchase, spend, return and adjustment, with who caused it and why, and which kind of credits each one used;
- its purchases: the pack bought, the price, Creem's checkout, order and customer identifiers, and what Creem reports as paid or refunded. We never receive or store card details;
- its approval threshold for AI assistants and each project's credit budget, if set.
Its first name. The workspace you get when you sign up is named for you: your name, or the
first part of your email address. If your address is at your own domain rather than an email
provider's, the domain alone (for example example.com, never your address or your name) is sent
to Anthropic to suggest your organisation's name for it. You can rename it at any time.
2.4 Your projects
For each project: its name; what you are naming and for whom, if you describe it; the candidate names; how far you have narrowed each one; the trademark classes you choose and your decisions about trademark records; each test run, what it asked for and what it cost; and the results your runs produced. A test run belongs to the workspace: its results show in every project of the workspace that holds the same name, so a name is not paid for twice. We also record when each name was added to a project, shortlisted or un-shortlisted.
Starter names. If you ask NameFactors to suggest names, your description of what you are naming, your brief and, in an existing project, the names it already holds (so they are not suggested again) are sent to each AI assistant you choose for the suggestions (Claude, ChatGPT, Gemini or Grok: Anthropic, OpenAI, Google or xAI) and kept with the suggestions they returned. This is the only place a project's description leaves NameFactors. When the last project made from a suggestion is deleted, the description and the suggested names are deleted too; only counts remain.
2.5 AI assistants you connect
If you connect an AI assistant (Claude, ChatGPT or another, over the Model Context Protocol), we record the assistant's client registration, the consent you gave, the workspace and permissions you granted it, its access tokens and sessions, and which runs and name generations it started. An assistant acts in the one workspace you chose for it. The Terms of Service say what an assistant may do.
2.6 Test results, which are not about you
A name's test results describe the name, not you:
- Speech recognition: recordings of synthetic voices speaking the name (we generate them; we never record you), what speech recognition heard, and the measurements derived from that.
- AI tests: each model's answers about the name.
- Domains: whether each domain checked was available, and any asking price a marketplace listed.
- US trademark screening: which records of the US trademark register matched, and the version of the register searched.
These carry no link to a person, a workspace or a project: they are stored without any association to whoever submitted the name. They are reused when anyone tests the same name, and kept after your project is deleted (§6). A candidate may itself be a person's name, and a model's answer about it may say something about an identifiable person; where it does, the rights in §7 apply to it.
2.7 In your browser
One cookie, namefactors_session, keeps you signed in; it is not readable by scripts and is sent
only over HTTPS. Browser storage holds a note that you are signed in, the workspace you last chose,
your display preferences and a few interface settings, as the Cookie Policy
lists. No analytics, no advertising, no session recording, no third-party scripts. If that changes,
this policy will change first, and where the law requires it we will ask before any tracking
begins.
3. Why we process it
| Purpose | What | Basis |
|---|---|---|
| Providing the service to you as our customer: your account, your workspace, projects, tests and results | §2.1–2.6 | performance of our contract with you |
| Providing the service to an organisation you work for: your account and your access to its workspace | §2.1–2.3 | our legitimate interest, and the organisation's, in administering its members' access; for the workspace's content, the organisation's instructions |
| Security: keeping accounts safe, limiting abuse, investigating incidents | §2.2 | our legitimate interest in keeping accounts and the service safe |
| Billing: running the credit ledger and purchases | §2.3 | performance of a contract |
| Keeping billing records after a workspace is closed | §2.3 | legal obligation (accounting and tax law) |
| Emailing you a sign-in code you asked for | §2.2 | performance of a contract |
| Sending you an invitation a member addressed to you | §2.3 | the member's and our legitimate interest in letting people join a workspace; you can ignore it, and it expires |
| Improving the measurements: reusing and aggregating a name's results, stored without association to any customer | §2.6 | our legitimate interest, assessed and recorded |
(The bases are named in the GDPR's terms. Israel's Protection of Privacy Law applies to us in any case; it does not use these labels.)
We do not profile you, make automated decisions with legal effects about you, sell your information, or use it for advertising.
Organisations. If you use NameFactors for an organisation, that organisation decides what goes into its workspace, and we process the workspace's content for it and on its instructions, under the Terms of Service (§6). Your account, sign-in and security records, billing, and the shared results in §2.6 are our own processing, which this policy describes.
4. Who else receives information
Companies that run the service and the tests are listed, with what each receives and where, on our Subprocessors page. In summary: our hosting, database, queue, storage and backups are in Frankfurt and elsewhere in the EU, and Cloudflare's global network handles connections to namefactors.com at the point nearest you before they reach Frankfurt; email is delivered by Resend; and each test sends the candidate name, and nothing about you, to the company that runs it: Deepgram (speech recognition), Anthropic, OpenAI, Google and xAI (AI tests), and Fastly (domain availability). Each receives names under its own terms for business customers; none receives your account details.
Creem sells the credit packs as merchant of record. When you buy credits you buy from Creem, under Creem's terms and privacy policy. Creem handles your card, taxes and refunds, and tells us that a purchase, refund or dispute happened and for which workspace.
Google Workspace hosts our mailboxes. Mail you send to privacy@ or support@namefactors.com, and our replies, are received and kept there.
The US Patent and Trademark Office publishes the trademark register we search. We search our own copy; nothing about you is sent to the USPTO.
The AI assistant you connect receives what it asks our service for, acting for you, under your own agreement with that assistant's provider.
Authorities, where the law requires it.
5. Where information is processed
Our servers, database, queue, storage and backups are in the European Union; connections to namefactors.com pass through Cloudflare's global network on the way. Syrenox Systems Ltd is established in Israel, which the European Commission and the United Kingdom recognise as providing adequate protection for personal data. Some of the companies named in §4 process information in the United States; transfers to them rely on the EU-US Data Privacy Framework, with its UK Extension, where the company is certified under it, and otherwise on the standard contractual clauses in our agreement with that company.
6. How long we keep it
| What | How long |
|---|---|
| Your account and workspaces | until deleted (§7) |
| Projects and candidates | until you delete the project |
| Your workspace's test runs and their results for a name | until no project of the workspace holds the name |
| Sessions | 7 days, or 90 days with "remember me" (ending after 30 idle days); deleted when you sign out or end them from your account page |
| Sign-in codes | 15 minutes |
| Rate-limiting records | the limit's window |
| AI assistant access tokens and refresh tokens | 15 minutes and 7 days; an assistant's session ends a day after its last request |
| Security records (§2.2) | 12 months |
| Credit ledger and purchases | for as long as the workspace exists, and as accounting law requires |
| A name's test results (§2.6) | indefinitely, with no link to you |
| When a name was added to or shortlisted in a project | deleted with the project |
| Starter-name descriptions | until the last project made from them is deleted |
| Requests about your information, and our answers | 3 years after the request is closed, longer while a complaint, dispute or legal obligation needs them; copies of identity documents and data exports are deleted once the request is done |
| Backups | daily backups for 14 days and weekly backups for 8 weeks, encrypted, in the EU. Deleted data remains in backups until they expire. |
7. Your rights and how to use them
Depending on where you live, you have the right to access the information we hold about you, correct it, have it deleted, receive a copy of it, object to or restrict some processing, and complain to a supervisory authority. For people in the EU and UK these rights come from the GDPR and UK GDPR; Israeli residents have rights under the Protection of Privacy Law.
To exercise any of them, email privacy@namefactors.com. We answer without undue delay and normally within one month; if a request is complex, or there are several, we may need up to two months more, and we tell you within the first month.
What you can do yourself:
- Delete a project. This deletes its candidates, decisions and budget, and the runs and results of every name no other project of the workspace holds. Results for a name another of its projects holds stay, for that project. It does not delete a name's test results (§2.6), which carry no link to you.
- Leave a workspace, or remove members if you are an owner or administrator.
- End sessions from your account page.
- Revoke an AI assistant's access from the Assistants page.
What you ask us for:
- Deleting your account. We delete your account, your personal workspace and its projects, and confirm when it is done. Your name, email address, sessions and security records go with it. A name's test results (§2.6) stay, with no link to you. The ledger of a workspace that bought credits is kept as accounting law requires. Deleted data leaves backups as they expire, within 8 weeks.
- A copy of your information.
- Deleting a workspace that other people are members of: its owner asks.
8. How we protect it
Information is encrypted in transit and at rest. Each workspace's projects are reachable only by its members, and the server decides which workspace a request acts in, never the browser. Passwords are stored hashed; IP addresses are reduced before storage. Results are shown to a project only through its own workspace's runs; we do not disclose what other customers have tested. Backups are encrypted before they leave our servers and stored in the EU. Access to production systems is limited to the people who operate the service. They can see account details, such as your name, email address and how you joined, where needed to administer accounts and admit people to the private beta.
If we learn of a breach affecting your information, we will tell you without undue delay, and notify the authorities as the law requires.
9. Who NameFactors is for
NameFactors is a service for businesses and professionals. It is not directed at children, and we do not knowingly collect information from anyone under 18. If you believe a child has created an account, email us and we will delete it.
10. Changes
When this policy changes, we update the date at the top and, for changes that matter to you, tell you in the app or by email before they take effect. The current version is always at https://namefactors.com/privacy, with a record of what changed and when (Changes, below).
11. Contact
Syrenox Systems Ltd, Israel, company number 517155438. Email: privacy@namefactors.com.
Changes
| Date | Change |
|---|---|
| 2026-10-26 | First published. |
| 2026-10-27 | Generating names sends the names a project already holds, so none is suggested again (§2.4). We record which version of the terms and of this policy you agreed to when you created your account (§2.1). |
| 2026-10-30 | Google sign-in: what Google sends us, how it is used, who sees it and how long it is kept, in full (§2.1). The people who operate the service can see account details where needed to administer accounts and the private beta (§8). |
| 2026-11-06 | A new workspace is named for you, and, for an address at your own domain, the domain alone is sent to Anthropic to suggest its name (§2.3). |
| 2026-11-07 | An AI assistant's session now ends a day after its last request, not an hour (§6). |
| 2026-11-21 | A workspace's test runs are the workspace's: a name's results show in each of its projects that holds the name, and stay until none does (§2.4, §6, §7, §8). |