The short version: we do not store the content of your prompts or the model's answers. We store what is needed to run an account and bill it correctly — who you are, how many tokens you spent, and what you paid.
1. Who is responsible
[LEGAL ENTITY NAME], [REGISTERED ADDRESS], is the controller of the data described here. Privacy questions and rights requests go to privacy@unbleep.ai.
2. What we do not store
Prompt and completion content is never written to our database. Your request is held in memory only for as long as it takes to forward it to the model provider and stream the answer back to you. Nothing in our schema has a column for message content, and our application logs do not record request bodies.
We also never see your card number: card details go straight to Stripe from their hosted checkout page and never touch our servers.
3. What we do store
Account. Your email address, the time the account was created, and — if you sign in with a password — a scrypt hash of that password. We never store the password itself. If you sign in with Google we store the account identifier Google gives us instead.
Sessions and API keys. Stored only as SHA-256 hashes, alongside a key's name, its first characters and last four digits so you can recognise it, and when it was last used. A key's full value exists only at the moment we show it to you.
Usage metering. For each request: a request identifier, the model called, input and output token counts, the computed cost, whether it succeeded, and the timestamp. Not the text.
Billing. Every credit and debit on your balance, and for each payment the processor used, its reference, the amount and the status.
Server logs. Our web server records the IP address, timestamp, URL and user agent of requests, as standard for operating and securing a service. Error logs may include diagnostic fragments returned by an upstream provider.
Support. Whatever you send us by email, for as long as needed to answer it.
4. Why we process it
To provide the service and authenticate you — performance of our contract with you.
To meter usage, bill accurately and keep an auditable ledger — contract, and our legal obligation to keep accounting records.
To detect fraud, abuse and key compromise, and to keep the service secure and available — our legitimate interest.
To send transactional email (password resets, payment receipts, service notices) — contract.
To measure how the site performs and where sign-ups come from — consent, where required.
5. Who else processes your data
We use a small number of providers to run the service. They act on our instructions, except where noted.
Model providers. Serving your request means sending your prompt to the provider hosting the model you chose — currently Abliteration and Featherless. What they do with it is governed by their own terms and privacy policies. If this matters to you, choose your model accordingly.
Stripe — payment processing. Stripe is an independent controller of the payment data it collects.
Google — only if you choose "Continue with Google", to verify your identity.
DigitalOcean — hosting. Our servers and database run in [REGION].
Analytics and advertising measurement — where enabled and where you have consented, we use analytics and conversion pixels to understand traffic and sign-ups.
We do not sell your personal data, and we do not use your prompts or outputs to train models.
6. Cookies
Essential. A session cookie keeps you signed in, and a short-lived cookie protects the Google sign-in flow. The service cannot work without them.
Analytics and advertising. Set only where enabled and, in regions that require it, only with your consent. You can decline without losing access to the service.
7. How long we keep it
Account data: while your account is open.
Sessions: until they expire. Password reset links: [TTL], single use.
Usage and billing records: retained after account closure for as long as accounting and tax law requires, because they are financial records.
Server logs: rotated on a short cycle in the ordinary course of operations.
8. Your rights
Depending on where you live — including under the GDPR in Europe, the LGPD in Brazil, and comparable US state laws — you may ask us to:
Confirm what we hold about you and give you a copy.
Correct anything inaccurate.
Delete your account and personal data, subject to records we must keep by law.
Export your data in a portable form.
Object to or restrict processing based on legitimate interests, and withdraw consent for analytics at any time.
Write to privacy@unbleep.ai and we will respond within the period the applicable law allows. You also have the right to complain to your local data protection authority.
9. Security
Traffic is encrypted with TLS. Passwords are hashed with scrypt; API keys and session tokens are stored only as hashes, so a copy of our database would not yield a usable key. Administrative access is restricted, the application runs under a sandboxed service account, and backups are held on the same restricted infrastructure. No system is perfectly secure; if a breach affects your data we will notify you and the relevant authority as the law requires.
10. International transfers
Your data is processed on servers in [REGION] and by the providers listed above, which may be located outside your country. Where the law requires it, transfers rely on standard contractual clauses or another approved mechanism.
11. Children
The service is not for anyone under 18 and we do not knowingly collect their data. If you believe a minor has an account, tell us and we will remove it.
12. Changes
We will post any update here and change the date at the top. Material changes will be announced by email or in the console before they take effect.
Draft for review
The factual claims here were checked against the running system — the database schema really has no column for message content. The marked fields still need your entity details, and counsel should review the document before launch.