Privacy Policy
Approved by the owner on 2026-11-06; placeholders still to fill. Not legal advice. The facts below match the product as built on 2026-11-06: hosted in Google Cloud us-central1, prompts kept out of logs, uploads deleted after 7 days and outputs after 30. Placeholders are in brackets. Check which privacy laws apply to you (for example the Australian Privacy Act, GDPR and UK GDPR, or US state laws) and adjust section 6 to match.
[COMPANY] ("we") runs [SERVICE]. This policy explains what personal information we handle when you use our website, dashboard, API and SDKs, and what choices you have. For account and billing data we are the controller. For content you send through the API on behalf of your own users, we act as your processor (section 6).
1. What we collect
| Category | Examples | Where it comes from |
|---|---|---|
| Account | Name, email address, organization, role, invitations | You, or a teammate who invites you |
| Sign-in | Session cookies, sign-in links, Google or GitHub account id, IP address and browser at sign-in | You, and Google or GitHub if you sign in with them |
| Billing | Top-ups, invoices, balance, card brand and last 4 digits (Stripe holds the full card details; we never see them) | You, through Stripe |
| Content | Prompts, uploaded images and video, generation settings, generated outputs | You, through the API or playground |
| Usage | Request ids, model, timing, cost, errors, API key ids (we store keys only as hashes) | Created as you use the service |
| Safety | Moderation results, flagged content, abuse signals, and an audit log of admin actions | Our systems and reviewers |
| Support | Emails and anything you send us | You |
We don't knowingly collect sensitive information. Don't put it in prompts or uploads.
2. How we use it
| Purpose | Data used | Legal basis (where GDPR applies) |
|---|---|---|
| Run the service: accounts, API requests, sending content to the model you chose, delivering outputs | Account, content, usage | Contract |
| Billing, invoices, fraud prevention | Billing, usage | Contract; legal obligation |
| Moderation and abuse prevention, including CSAM detection and reporting | Content, safety, usage | Legitimate interests; legal obligation |
| Security, debugging and reliability | Sign-in, usage (prompts are not written to logs) | Legitimate interests |
| Service emails: sign-in links, receipts, alerts, policy changes | Account | Contract |
| Product updates by email, which you can turn off | Account | Consent or legitimate interests |
We don't sell personal information, use it for targeted advertising, or use your content to train AI models. Model Providers handle your content under their API terms; see section 3.
3. Who we share it with
We share personal information only with the service providers below, when the law requires it, or in a merger or sale (with notice to you). Keep this list current on a public subprocessors page.
| Recipient | What for | Data | Location |
|---|---|---|---|
| Google Cloud | Hosting, database, storage, logs | All categories | USA (us-central1) |
| Stripe | Payments and invoices | Billing, email | [Confirm per Stripe account] |
| [Resend] | Sign-in and service emails | Email address, email content | [Confirm] |
| Google, GitHub | Sign-in, if you choose it | Account id, email, name | Per provider |
| Model Providers: Google Vertex AI, OpenAI, xAI, MiniMax, Black Forest Labs, Alibaba Cloud Model Studio, BytePlus | Generating the output you asked for | Prompts, uploads, settings for that request only | Per provider; Alibaba Cloud in Singapore; [confirm others] |
| [CSAM hash-matching vendor] | Detecting known child abuse imagery | Uploaded and generated images | [Confirm] |
| Authorities such as NCMEC or [LOCAL AUTHORITY] | Reports the law requires | Flagged content, account details | [Varies] |
Only the Provider of the model that runs a request receives its content. If you allow fallback routing, a request may go to another Provider on the list.
4. How long we keep it
| Data | Kept for |
|---|---|
| Uploaded inputs (images, video, audio) | 7 days |
| Generated outputs | 30 days by default, or your plan's period |
| Prompts and generation records | [12 months], then deleted or anonymized; the billing fields stay with the financial records |
| Account data | While your account is open, then [30] days |
| Billing and ledger records | [7] years, or as long as tax law requires |
| Logs and traces | [30] days |
| Database backups | 7 days (rolling) |
| Content and records preserved for a CSAM report or legal hold | As long as the law requires |
Deleted data leaves backups as they roll over, within 7 days.
5. Transfers and security
- Transfers. We store data in the United States, and Providers may process it in other countries (section 3). Where the law requires safeguards for transfers, such as from the EU, UK or Australia, we rely on [Standard Contractual Clauses / the UK Addendum / reasonable steps under APP 8] in our agreements with each recipient.
- Security. Data is encrypted in transit and at rest; secrets use keys we manage in Cloud KMS. API keys are stored only as hashes. The database is on a private network, access is limited by role, admin actions are logged, and outputs are delivered through links that expire after an hour.
- Breaches. If a breach affects your personal information, we'll tell you and the regulators as the law requires.
6. Your rights
- Depending on where you live, you can ask to access, correct, delete or export your personal information, to object to or restrict some uses, and to withdraw consent. Californian residents also have the right not to be discriminated against for using these rights. We don't sell or "share" personal information as the CCPA defines it.
- Email [PRIVACY EMAIL]. We'll confirm who you are and reply within [30] days. You can delete generations and outputs yourself in the dashboard or through the API at any time.
- You can complain to your local regulator, for example the OAIC in Australia, your EU supervisory authority or the UK ICO. Please contact us first so we can try to fix it.
- If you build on [SERVICE]. When your app sends your own users' content through our API, you are the controller of that data and we process it on your instructions under our [Data Processing Addendum]. Your users should contact you; we'll help you answer them.
7. Cookies, children, changes and contact
- Cookies. We use only the cookies needed to keep you signed in and to protect sign-in. We don't use advertising or third-party analytics cookies, so there's no cookie banner. If that changes, we'll update this section and ask for consent where required.
- Children. The service is for people aged 18 and over. We don't knowingly collect children's personal information; if you think we have, tell us and we'll delete it.
- Changes. We'll post updates here and email account owners about material changes at least [30] days before they take effect.
- Contact. [COMPANY], [ADDRESS], [PRIVACY EMAIL].