Privacy policy
What poddub collects, who processes it, where it runs and how long it is kept.
Version 2026-09-06Effective 2026-09-06
The version is the date this text took effect, and it is the version an account's consent record names.
About this policy
poddub is operated by Seats at, LLC, a Delaware limited liability company. This policy covers the poddub iPhone app, the poddub API, this site and the public show pages poddub serves for its customers.
It carries a version, and that version is the date it took effect. The same version is the one an account's consent record names, so the list of providers below and the list the app shows at sign-in cannot drift apart.
Information we collect
Your account: the email address you sign in with. Sign-in is a code sent to that address, so there is no password; the code is stored hashed and expires.
Your session: when you sign in, poddub records the session and its expiry, with the IP address and the browser or app that created it.
Your organization: its name, its handle, its teams, who belongs to which, each person's role, and the addresses invitations were sent to.
What your team creates: the text pasted in as a source, and recordings uploaded where the operator has switched that on; the scripts generated from them, the audio, the chapters, the transcripts, the artwork, and who made each of them.
Your consent: the version of the provider list you accepted, when you accepted it, and whether you withdrew it.
Your subscription: which plan an organization has and when it expires, reported by the App Store through RevenueCat against your account id. Card details never reach poddub.
Feed fetches: when a private feed or an episode file is fetched with a personal listener address, poddub records that address's token, the episode, the time and the podcast app's user agent. No IP address is kept there.
Reports: what somebody reports about a public show or a public episode, the reason they give, the contact address they choose to leave, and their account id if they were signed in.
Sign-in attempts: failed attempts per email address, so that an address can be closed for a while after too many of them.
This site sets no cookies, runs no advertising and carries no third-party analytics.
poddub is not for children. An account is made by an adult acting for a company, and poddub does not knowingly collect information from children.
How we use and share information
poddub uses what it collects to run the service: to sign you in, to hold your organization and its teams, to generate the episodes your team asks for, to deliver them to the right feeds and to the app, to apply the seats and the minutes your plan carries, and to answer support requests and abuse reports.
poddub sends no marketing email. The only messages it sends are sign-in codes, invitations, notifications that something was reported, and the confirmation of an account deletion.
poddub does not sell personal information and shares none of it for advertising.
Information reaches the providers named below, which handle it to run the service; it is disclosed where the law requires it, or where it is needed to protect people or the service itself.
If the business is sold or merged, the information moves with it, and this policy holds until it is replaced by one at least as protective.
Who processes the text of your episodes
Turning documents into episodes means sending their text to AI providers. Every one of those calls goes through the Vercel AI Gateway, which carries the request to the provider named below and returns the answer. This table and the list the app shows you at sign-in are rendered from the same source, so they cannot disagree.
| Provider | What it does | Where it runs |
|---|---|---|
| Vercel AI Gateway | Routing | United States |
| Anthropic | Scripts | European Union |
| Fish Audio | Voices | United States |
| OpenAI | Voices, fallback | United States |
The Gateway states that it keeps nothing once a request has completed. What each provider keeps is governed by that provider's own terms.
Who else processes your data
Vercel hosts this site, runs the API and holds the private file store; the store is in the European Union, and the functions run in the European Union region set at deployment.
The report form on a public show page is protected by Vercel BotID, which inspects the browser sending a report to tell a person from an automated client; Vercel runs it on Kasada. It applies to that one request and to nothing else on the site, and a report refused by it is not recorded.
Neon runs the database, in the European Union.
Resend delivers the sign-in codes, the invitations, the report notifications and the deletion confirmations.
RevenueCat records which plan an organization has, against an account id, from the purchases Apple reports.
Apple takes the payment for a subscription and handles its renewal and cancellation.
Resend, RevenueCat and Apple are United States companies and process what reaches them outside the European Union.
Transfers outside the European Union
Sources, scripts, audio and every database row are stored in the European Union.
Script generation is pinned to European inference: each request names the European Union as its region, the provider runs it there and keeps anything it keeps there, and a request that region cannot be honoured for fails rather than running somewhere else.
Speech generation is not pinned, because no voice engine in the catalogue offers a region. A script's text and the audio that comes back are processed in the United States.
Two things sit outside that pin. The Gateway's own handling of a request can terminate in any of its regions before it forwards it, and a request a provider flags for abuse or safety review is handled under that provider's policies, which can fall outside the region.
The legal basis for these transfers is reviewed before the service is released.
How we protect information
Traffic is served over HTTPS. The database and the file store are in the European Union, and the file store is private: audio, chapters, transcripts and artwork are fetched through short-lived signed addresses issued for one request at a time.
Sign-in codes are stored hashed and expire, and too many failed attempts close an address for a while.
A personal feed address carries a secret. Anyone holding it can fetch that feed, so treat it as a password: you can rotate it in the app, which stops the old address at once, and losing your place in a team or an organization stops your addresses for it.
No service is perfectly secure, and this one does not claim to be.
How long we keep it
Sources: until your team deletes them, or until the organization is deleted.
Scripts: with the episode they belong to.
Intermediate audio: deleted when the episode is finished. After a failure it is kept so a retry can resume, for the organization's retention window - 7 days unless its administrators set another, which they may set between 1 and 30 days.
Finished audio, chapters and transcripts: until the episode is unpublished, which deletes them; a public copy until the release is retracted, which deletes the copy.
Feed fetch records: 30 days.
Reports: kept as the operator's record of what was reported and what was done about it.
Consent records: kept as the record of what you accepted and when.
Sessions: until they expire or you sign out.
Deleting an account removes what belongs to it, as the next section describes.
Your rights
You can see your account and your organizations in the app. Your team can edit and delete the sources it added, and an owner or an admin can unpublish an episode, which deletes its audio.
You can withdraw your consent to the providers above at any time in the app's settings. Creating episodes stops; listening keeps working.
You can delete your account in the app, as the next section describes.
There is no marketing email to unsubscribe from.
For anything else - a copy of your data, a correction, a complaint - write to hello@poddub.com and say what you are asking for.
Deleting your account
Deletion is in the app's Settings. Before it runs, the app shows which organizations block it and which would be deleted with the account.
If you are the only owner of an organization that has other members, you must make another member an owner first. An organization where you are the only member is deleted with your account, and its episodes, feeds and files go with it.
Episodes and sources you made for an organization you share with other people stay with that organization.
When the deletion runs, your sessions and your listener addresses stop working at once and the account's rows are removed. A confirmation is sent to your address.
Deleting the account does not cancel an App Store subscription. Cancel that in the App Store.
When the provider list changes
Adding a provider, removing one or moving one to another region changes what you were told, so it changes this policy's version. The current version is 2026-09-06.
Everyone who accepted an older version is asked again in the app before they create anything else. Listening is not affected.
Links to other websites
This site and the app lead to places poddub does not run: the App Store, a podcast app, a customer's own public show. This policy does not cover them, and poddub is not responsible for what they do with what you give them.
Changes to this policy
When this policy changes, its version changes with it and the new text is published here. A change that adds a provider or moves one also asks everybody to accept the list again in the app before their next creation.
Contact
Write to hello@poddub.com. The operator is Seats at, LLC, a Delaware limited liability company.