Privacy and sub-processors
Last updated 20 September 2026. This page is written to be checkable: every claim on it corresponds to something the system enforces, and where something is not enforced it says so instead of being left out.
The short version
- Audy is not storage. Audio you send is processed and deleted. Results go to your bucket when you give one.
- Your audio reaches one third party: Amazon Web Services,
in
us-west-2. No transcription service, no AI vendor, no analytics provider. - Nothing you send is used to train anything.
- This website has no cookies, no analytics and no third-party scripts. The only network request it makes is to Audy's own API, when you submit the signup form.
- Audy never receives your card details, and never asks for cloud credentials of yours.
What Audy collects, and why
| What | Why it exists |
|---|---|
| The audio or video you submit | It is the thing being processed. Held only for the length of the job — see retention below. |
| Your email address | To verify the account at signup, and to reach you about the service. Optional fields are optional: a display name is stored if you give one. |
A hash of your address with any +tag removed (and, for
Gmail, its dots), and the network you signed up from: the first three
parts of an IPv4 address, or the first 48 bits of an IPv6 one, never
the full address |
So the free starting credit goes once to each inbox, however its address is spelled, and only a few times a day to one network. Erased with the account. |
| API keys | Stored as a SHA-256 hash plus the first 16 characters, so a key can be recognised and displayed in a list. The key itself is shown once, at creation, and is not stored — if you lose it, Audy cannot recover it and can only issue a new one. |
| Job records: which account, which workflow, status, timings, and the processing chain that produced each result | The receipts the product is built around, and the basis for debugging a job you ask about. |
| Usage events: an account id and a number of audio seconds | Billing. Raw seconds are stored and rounded only when an invoice is produced. |
| Your IP address, on requests that fail authentication and on rate limiting | Abuse and credential-stuffing defence. It is read from a fixed
position in X-Forwarded-For rather than the value a caller
supplies, because a forged one would poison the same alarm it feeds. |
Where it runs
Two places, both under Audy's sole control:
- Amazon Web Services,
us-west-2(Oregon, United States) — the API, the database, the job queue and temporary object storage. - Audy-operated hardware in the United States — the machines that run transcription and audio processing. These are Audy's own computers, not a rented service, and no third party has access to them.
Per-task isolation, a working space wiped when the task ends, and encryption in transit and at rest apply identically in both places.
Sub-processors
Only two entries, and the second one only exists after payment is sent.
| Who | What they receive | Where | What for |
|---|---|---|---|
| Amazon Web Services | Audio during processing, account records, job records, logs, and your email address when a verification message is sent | United States (us-west-2) |
Compute, storage, database, email delivery |
| Stripe | Your Audy account ID (an opaque identifier), and a count of audio minutes per billing period, plus whatever you give Stripe directly on its own checkout page. | United States | Payments and metered billing |
Two important details about Stripe: Audy does not send Stripe your email address — Stripe collects whatever it needs at checkout, directly from you. And Audy never sees your payment details, which are entered on Stripe's page, not Audy's, and nothing resembling a card number passes through or is stored by Audy.
No audio and no transcript is ever sent to Stripe, or to anyone else beyond AWS. Transcription runs on Audy's own hardware.
How long things are kept
| Data | Retention |
|---|---|
| Audio you upload, and results Audy holds | Deleted within 24 hours by a storage lifecycle rule, independently of the application. A task's working space is wiped when the task ends, which is usually sooner. |
| Account record, projects, API key hashes | Until you ask for the account to be deleted. |
| Job records and usage events | Kept as billing and audit records. |
| Application, access and database logs — including the IP address on a failed authentication | 14 days, then deleted automatically. |
| Rate-limit counters, keyed by IP address or by a hash of an API key | Expire on their own: about two minutes for the request limit, two hours for the signup limit. |
After you delete an account: a one-way hash of the
email address (with any +tag removed, and Gmail's dots), and
the number of starting-credit minutes it has already been given |
Kept indefinitely — this is what stops the same address collecting the free starting balance over and over by deleting and signing up again. The address itself is erased; the hash cannot be turned back into it, so nobody can read this and learn who deleted their account. It can only answer a question about an address someone already has. |
| Email addresses that hard-bounced or complained | Kept, deliberately, even after the account is gone — see below. |
That last row is the one exception to "delete the account, delete the data", so here is the reasoning rather than a footnote. When a mail provider tells Audy an address is undeliverable, or someone marks a message as spam, that address is recorded so nothing is ever sent to it again. It is a fact about an inbox rather than about a customer: the same address may sign up again later and it is still undeliverable. Discarding it would mean mailing a known-bad address a second time, which is how a sending domain gets blocked for everyone using it. If you want that record removed as well, ask, and it will be — with the consequence that Audy will try to mail you again.
What Audy does not do
- No training. Your audio, transcripts and workflows are not used to train or evaluate any model.
- No third-party audio processing. No transcription API, no hosted model, no "AI partner." Processing happens on AWS compute that Audy controls and on Audy's own machines.
- No selling or sharing of personal data, and no advertising or data-broker relationships of any kind.
- No cookies, analytics or trackers on this site. There are no third-party scripts on this page at all.
- No fetching of arbitrary URLs. Audy reads and writes object storage you name; it will not go and fetch a link for you, which keeps the decision about what to download yours.
- No cloud credentials of yours. Access to your bucket is granted by your own bucket policy, so there is no access key for Audy to hold, leak or need rotating.
Requests about your data
Email hello@audy.dev from the address on the account and say what you want: a copy of what is held, a correction, or deletion. Audy aims to answer within 30 days and in practice much sooner.
Deletion you can also do yourself: DELETE /v1/account, with your
API key and your email address. That sends a confirmation code to the
address; calling the same endpoint again with the code is what actually
deletes. Three things are needed and each rules out a different mistake —
the key proves access, the address proves you know whose account it is (no
endpoint here will tell you), and the code proves you can read the inbox. A
stolen key gets as far as sending you an email about it, and no further.
It is a code to paste rather than a link to click, on purpose. Mail security scanners and link previewers follow links in incoming messages, and a link that deleted an account would be followed by one of them before you had read the sentence explaining what it did.
Two more things you can do without asking anyone: revoke an API key, and delete the audio Audy holds — and the second is the default, since it happens within 24 hours whether you ask or not.
What deletion leaves behind, exactly. Your address, your name, your workflows, your presets, your uploads, your webhook endpoints and your runners are erased. Job records keep their timings and durations and lose everything you wrote into them — the bucket you named, the filenames, the results. Usage events and credit entries are kept in full, because they are the billing record and an account that owed money before deleting still owed it after. And one hash, in the table above.
Where this is not finished
The same section the front page has, for this subject. These are true today and each is a thing to fix rather than a position.
- Deletion has no recovery window. Once confirmed it takes effect immediately and cannot be undone — there is no thirty-day grace period to change your mind in. That is the honest reading of "the data is gone", and it does mean a mistake is permanent.
- There is no signed Data Processing Agreement to hand you yet. If you need one before you can use Audy, say so — it moves up the list quickly with a real name attached to it.
- All processing is in the United States. There is no EU or UK region, so if your data cannot leave a particular jurisdiction, Audy is not yet a fit. Nothing on this page pretends otherwise.
Questions about any of this: hello@audy.dev.