Draft. A lawyer has not read this page yet, so it isn't in force. Highlighted passages are gaps for counsel to fill.
Privacy policy
Who is responsible
[LEGAL ENTITY NAME: placeholder], of [REGISTERED ADDRESS: placeholder], is the controller of account, billing and usage data. For files you upload we act as your processor, under the data processing agreement.
What we hold
| Data | What it is | Why |
|---|---|---|
| Sign-in | Held by Supabase Auth: your email and a hashed password if you sign up with them, or your GitHub user ID, email and profile details if you use GitHub | To sign you in |
| Account | A bare user ID, status, balance, amounts owed, first payment date | To run your account |
| API keys | A SHA-256 hash, a short prefix, the name you gave it, when it was last used | To authenticate you. We can't recover a key |
| Payments | Pack, amount, Stripe session and payment IDs, an opaque card fingerprint. Stripe holds your card details. We never see them | To add packs to your balance and limit launch seats to one per card |
| Usage | File IDs, content type and size, item counts, units, states, error codes, timestamps. No filenames | To run the queue and bill you |
| Your files | Inputs and outputs, including transcripts. These live in object storage only, never in our database. The store's index keeps each file's random key, size, type and time, and no content and no filename | To do the work you asked for |
| Logs | Operational logs. They exclude URLs, tokens, filenames and transcript text | To keep the service running |
For counsel: lawful basis for each row.
How long we keep it
| Data | Kept for |
|---|---|
| Uploaded files | 7 days from upload, then deleted by a job that runs hourly. Deletion starts at 7 days and normally finishes within a further day. |
| Output files | 7 days from when the item finished, then deleted the same way. Deletion starts at 7 days and normally finishes within a further day. |
| Records of finished items | 90 days |
| Records of cancelled items and expired files | 7 days |
| Submissions and the balance ledger | Kept for accounting. For counsel: the statutory period. |
| Payment records | Pack, amount, Stripe references and the card fingerprint. Kept for accounting and to limit launch seats to one per card, including after you delete your account. For counsel: the statutory period, and how long a fingerprint may be kept. |
What we don't do
- We don't sell personal data.
- We don't use your files or outputs to train models.
- This site runs no analytics and no advertising cookies.
Your browser
Public pages set no cookies of ours. When you sign in, the dashboard keeps your session in your browser's local storage. Signing out removes it. The landing page asks our API for the number of launch seats left, and Cloudflare, which serves the site, sees your IP address in the normal way.
Who receives it
The companies that run parts of the service for us are listed on the subprocessors page.
For counsel: international transfers and the safeguards relied on.
Deleting your account
Ask us and we delete your sign-in record, and remove your files and outputs from storage. A file we miss goes with the hourly deletion job, on the timetable above. The account, its ledger and its payment records, including Stripe references and the card fingerprint, stay under a bare ID with the status deleted. That ID no longer links to your email or GitHub identity.
Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict or export your data, to object to processing, and to complain to a regulator. To use them, write to [PRIVACY EMAIL: placeholder].
For counsel: data protection representative, regulator details, and any state or national additions.
Changes
We'll post changes here and tell you before anything material takes effect.