What we store, why, who else sees it, and how to get it back or deleted. Every item below corresponds to something the software actually does.
This document is not finished, and it is not ready to be verified.
Paddle reads this page to confirm who is selling. The facts below are not set on this deployment, so the page cannot state them — and no placeholder has been invented in their place, because a wrong company name on a policy page is worse than a missing one. Set these and this notice disappears.
[set LEGAL_ENTITY_NAME], of [set LEGAL_ADDRESS], is the controller of the personal data described here. For anything in this policy, write to [set SUPPORT_EMAIL].
This is the whole list. It is the schema, not a summary of it.
| What | Why |
|---|---|
| Email address, name and avatar URL | To identify your account and show you to your teammates. |
| Your organisation, its members and their roles | So the right people can see the right projects. |
| Briefs, projects, discovery runs, saved names and comments | This is your work. It is the product. |
| Subscription plan, status and Paddle identifiers | To know what you have paid for. No card details. |
| Monthly usage counts | To apply the limits on your plan. |
| An audit log of significant actions, including the IP address they came from | So an account owner can see who changed what — required for the audit trail we sell on the higher plans. |
| API keys, stored only as a hash | So a key readable from a database backup is not a working key. |
We never see your card. Payment details are entered on Paddle’s checkout and go to Paddle, not to us. We store only the identifiers Paddle returns so we know which subscription belongs to which organisation.
To provide the service you asked for, which is the contract between us: your account, your projects and your subscription. To meet legal obligations, such as keeping records of what was sold. And, for the audit log and the usage counters, because we have a legitimate interest in the service being secure and in plan limits being applied accurately.
We do not sell your data, we do not share it for advertising, and we do not train models on your briefs.
These are the only third parties involved, and each one is named with the part of the codebase that talks to it, so the claim is checkable.
Supabase · Authentication and database
Your email address, name, avatar if you sign in with a provider, and everything you create in the product — briefs, projects, runs, saved names and comments.
lib/saas/supabase.ts, supabase/migrations/
Paddle · Payments, as merchant of record
Your billing details and card. Paddle sells to you and takes the payment; card details are entered on Paddle's checkout and never reach our servers. We store only the customer and subscription identifiers Paddle gives us.
app/api/paddle/webhook, components/billing/
Vercel · Hosting
Ordinary request data — IP address, user agent, and the pages requested.
deployment
Google · Generating the one sentence explaining why a name suits a business
The business description from your brief and the candidate name. Only when the operator has configured a key; without one this step does not run and no data is sent.
lib/engine/licensing.ts
Domain registries (RDAP) and public registers · Checking whether a name is taken
The candidate names themselves. These are sent to public registries to ask whether a domain or handle is free. No personal data is included.
lib/omega/rdap.ts, lib/omega/presence.ts
These providers operate internationally, so your data may be processed outside your country. Each is engaged under terms requiring it to protect the data and to process it only on our instructions.
We set a session cookie so you stay signed in. That is a necessary cookie — without it, signing in would not persist — and it is the only category we set. There is no advertising cookie, no analytics profile and no third-party tracker on this site.
Paddle sets its own cookies on its checkout, governed by Paddle’s privacy policy.
Your work is kept while your account exists, because deleting a customer’s projects on a schedule would be deleting the product. Audit records are kept longer, since their purpose is to show what happened after the fact.
When you close your account we delete your personal data and your projects within 30 days, except where we must keep a record of a transaction for accounting or tax purposes. Export your work before you close the account if you want to keep it.
You can ask for a copy of your data, ask us to correct it, ask us to delete it, object to how we use it, or ask us to send it to someone else. Write to [set SUPPORT_EMAIL] and we will respond within 30 days.
If you are in the EU or UK and you think we have handled your data badly, you can complain to your national data protection authority. We would rather you told us first.
Access to your organisation’s data is enforced in the database itself, by row level security policies that deny by default — not only in the application code. API keys are stored as hashes, so a key readable from a backup is not a working key. Passwords are handled by our authentication provider and are never stored by us in any form.
No system is perfectly secure. If a breach affects your personal data we will tell you and the relevant authority without undue delay.
If we change this policy in a way that materially affects you, we will tell you before it takes effect. See also our terms of service.
The other documents: Terms of service · Privacy policy · Refund policy