Privacy Policy
Last updated
("we", "us") operates (the "Service"). This policy explains what personal data we process when you use the website, dashboard and API.
1. What we collect
| Data | Why | How long |
|---|---|---|
| Account: email, sign-in provider, display name, and optional company, website and use case | To run your account, contact you about it, and prevent free-allotment abuse | Until you delete your account |
| API keys: a one-way hash of each key, its name, prefix and limits | To authenticate requests. We cannot recover a key from the hash. | Until you delete your account |
| Request logs: time, endpoint, voice, format, character count, audio length, latency, cost, status | To show you your usage logs and to debug problems | 30 days. Not written under ZDR. |
| Input text of each request | So you can open a log entry and see exactly what you sent | 30 days. Not stored under ZDR. |
| Billing records: daily character, request and cost totals per key; credit ledger; Stripe customer id; card brand and last four digits | To bill you accurately, issue refunds and meet accounting obligations | As long as required by tax and accounting law (typically 7 years), including after account deletion |
| Cloned voice profiles: an encrypted numeric voice profile derived from your recording | To generate speech in that voice | Until you delete the voice or your account |
| Consent records: the version and fingerprint of the terms you accepted, the name you typed, the time, your browser user agent and a salted hash of your IP address | To show that cloning terms were accepted, and to respond to misuse reports | For the life of the account and up to 6 years after, for legal defense |
24-hour download files (only if you request delivery: "url") | So you can download the audio later | Deleted automatically within about 24 hours |
What we never keep
- Generated audio. It streams straight back to you, except the opt-in 24-hour download links above.
- Your voice recordings. A reference clip is decoded in memory, turned into an encrypted voice profile, and discarded.
- Full card numbers. Payments are handled entirely by Stripe.
- Raw API keys. You see a key once, at creation.
2. Zero data retention (ZDR)
You can turn on ZDR for your whole account or for individual API keys. With ZDR on, we write no request log and store none of your input text for those requests; text is processed in memory and discarded when the request finishes. We still record daily character, request and cost totals, because those are your billing records and contain no content. ZDR does not change how cloned voices or 24-hour download files work, so don't request delivery: "url" if you need nothing stored.
3. How we use data
- To provide, secure and support the Service, including fraud and abuse prevention.
- To bill you, have Stripe send payment receipts, and email you about important account, billing, service or policy changes.
- To investigate credible reports of misuse, such as unauthorized voice cloning.
We do not sell or share personal data for advertising, and we do not use your input text, recordings, voice profiles or output to train or improve models. Our staff access your content only when you ask for support, or when needed to investigate abuse, comply with law or secure the Service.
4. Service providers
We use these providers to run the Service. Each processes data only on our instructions.
- Cloudflare: website hosting, the API gateway, databases and file storage.
- Google Cloud: Firebase Authentication (sign-in) and Cloud Run (speech synthesis, which processes your text and voice profiles in memory).
- Stripe: payments and saved payment methods.
- Google Fonts: web fonts on our website. Your browser requests them from Google, which receives your IP address.
- Sign-in providers you choose (Google or GitHub) share your email and basic profile with us when you sign in.
Data may be processed in the United States and other countries where these providers operate. Where required, transfers rely on appropriate safeguards such as Standard Contractual Clauses.
5. Cookies and local storage
We use no advertising or analytics cookies. The dashboard keeps your sign-in session in your browser's storage (managed by Firebase Authentication), and we store a small flag so the marketing pages can show a "Dashboard" link. Sign-up may use Cloudflare Turnstile, a privacy-preserving bot check.
6. Your rights
Depending on where you live (for example, under the GDPR, UK GDPR or California law), you may have the right to access, correct, delete, export or restrict processing of your personal data, and to object to processing. Most of this is self-serve:
- Correct your profile on the Profile page.
- Delete your account on the Profile page. This revokes all keys, deletes cloned voices, request logs and stored input text, and removes your profile details. We keep billing records and consent records as described above.
- Export your request logs as CSV from the Logs page.
For anything else, email . We respond within 30 days. You may also complain to your local data protection authority. Our legal basis for processing is performance of our contract with you, our legitimate interests in securing the Service and preventing abuse, and compliance with legal obligations.
7. Security
Data is encrypted in transit (TLS) and at rest. Voice profiles are additionally encrypted with a key held only by the synthesis service. API keys are stored only as hashes. No system is perfectly secure; if a breach affects your data, we will notify you as required by law.
8. Children
The Service is not intended for anyone under 18, and we do not knowingly collect their data.
9. Changes
We will post updates here and email you about material changes before they take effect.