Back to AudioForge
Privacy

Privacy policy

What we collect, why we collect it, and the choices you have. Last updated October 29, 2026.

What we collect

Account information: your name, email address, and password (stored as a hash), or your Google account details if you sign in with Google.

Your content: the manuscripts and chapters you upload, the scripts, character and voice choices you create, the corrections you make in the Studio (like fixing a speaker, a tone, or where a sound effect belongs), and the audio files we generate for you.

Payment information: purchases are processed by Stripe. We never see or store your full card details — we keep only transaction records (what was bought, when, and for how much).

Usage data: product analytics events, device and browser information, and server logs (including IP addresses) used to operate and secure the service.

Support messages: bug reports and feedback you send us through the app.

How we use it

To provide the service: parsing your chapters, generating and stitching audio, storing your projects, and managing your token balance.

To improve the product: aggregate analytics tell us which features are used and where authors get stuck.

To keep the platform safe: preventing abuse of free tokens, fraud, and attacks on the service.

To support you: responding to bug reports, feedback, and support emails.

To make parsing better: when you correct AudioForge's work in the Studio — reassigning a speaker, changing a tone, splitting a segment, placing a sound effect — we keep a record of that correction and use it to evaluate and improve our parsing quality. This stays inside AudioForge: your corrections are never sold, never shared, and never used to train third-party AI models.

We do not sell your personal data, and we do not use your manuscripts for anything beyond producing your audio and the quality improvement described above.

Service providers we share data with

We share the minimum data needed with the providers that power AudioForge: OpenAI (chapter text, for script parsing), ElevenLabs (segment text, for voice generation), Stripe (payments), Cloudflare (hosting and private file storage for your audio and covers), PostHog (product analytics), and Google (only if you use Google sign-in).

Each provider processes this data to deliver its part of the service under its own data-processing terms.

Cookies and browser storage

We do not use advertising cookies, and we do not let third parties track you across other sites.

Essential cookies keep you signed in and remember small settings, such as whether you have finished the welcome setup on the listening site, your time zone for notification times, and the free chapters you have heard as a guest.

Analytics on the Studio: our analytics provider (PostHog) keeps a random identifier in a cookie and in your browser's local storage so that visits from the same browser are counted together.

Between audioforge.ai and studio.audioforge.ai we keep a few first-party cookies so moving from one to the other works: one marks that this browser has a studio sign-in (it holds no password or sign-in token), and others carry the campaign or invite code you arrived with until you sign up, and the page to return to after signing in.

Analytics on the listening site (app.audioforge.ai): when you open an author's reader link or play a free chapter without signing in, we set a first-party cookie named af_anon. It holds a random identifier, no personal details, and lasts up to one year. We use it only to count the steps from opening a reader link, to playing the first chapter, to unlocking a chapter, as one visit. If you then sign in, we link that identifier to your account so those steps count as yours. You can delete it at any time by clearing your cookies for the site.

Your content stays yours

You keep full ownership of your manuscripts and the audio generated from them. See our IP Policy & FAQ for the details on your rights, delisting, and deletion controls.

Your audio files are stored in a private bucket and served through expiring, signed links — they are not publicly listable.

Retention and deletion

We keep your content for as long as your account is active so you can keep working on your books. You can delete individual books, chapters, and their audio at any time from within the app, and deletion removes the files from our storage.

If you want your entire account and its data removed, contact us and we will take care of it.

Security

All traffic to AudioForge is encrypted in transit (HTTPS). Access to your content requires authentication, and stored audio is only reachable through signed, expiring URLs.

Changes and contact

If we make material changes to this policy, we will announce them in the app before they take effect.

Questions about your data? Email us at audioforge.ai@gmail.com.