Podidex

Privacy policy

Updated 4 November 2026

This policy explains how Yield Compiler AB handles personal data when you use Podidex: the iPhone and Android apps, the web app at app.podidex.com and the website podidex.com.

1. Who we are

Yield Compiler AB (org. no. 559433-1323), Anckargripsgatan 3, 211 19 Malmö, Sweden, operates Podidex and is the controller for the personal data described in this policy. Contact us at privacy@podidex.com. We have not appointed a data protection officer; send any privacy question to the same address.

Podidex is intended for adults aged 18 and over. We do not knowingly allow children to hold accounts. If you believe a child has created an account, contact us and we will delete it.

2. Summary

  • We use your information to create and deliver the podcasts you ask for. We do not sell personal data, show ads, send marketing emails or use your content to train AI models.
  • AI providers process your ideas, sources and scripts to generate episodes. In Live, your voice is sent to Google Gemini while you talk; we do not record it.
  • Website analytics and session recordings run only if you accept them. The mobile apps contain no analytics or advertising tracking.
  • Your account data is stored in the EU (Frankfurt). Some providers process data outside the EU/EEA; section 8 explains the transfer routes and how to request information about the applicable safeguards.
  • You can access, export, correct and delete your data, and you can delete your account in the app.

3. Information we collect

We collect information from you, from your use of Podidex, from sources and search services used for your episodes and from Stripe for website subscriptions and the current test-only iPhone external-purchase flow.

  • Account: email address, name, password (stored only in hashed form by our sign-in provider), sign-in codes and the result of security checks. If you create a podcast on our website before signing up, we use a temporary anonymous account and move the podcast to your account when you sign up.
  • Your podcasts: ideas, answers to clarifying questions, source addresses, instructions, voices, schedules and settings.
  • Generated content: scripts, titles, summaries, research notes, source text collected for your episodes, episode audio and podcast knowledge (facts and topics taken from earlier episodes so later episodes can build on them).
  • Listening and usage: listening progress, generated minutes and plan usage, ratings, feedback, content reports and Live session records (start and end time, minutes and technical usage).
  • Live: microphone audio while you are in a Live conversation, the name the host uses for you and the questions sent for a web lookup.
  • Devices: push notification tokens, platform and app version. Your session, library cache, downloads and settings are stored on your device.
  • Subscriptions: customer and subscription identifiers, plan, billing address, invoices, payment status, purchase channel, checkout offer, accepted terms and immediate-start request. Website subscriptions and iPhone test transactions have separate billing records. Stripe handles card details; we never see full card numbers.
  • iPhone external-purchase reporting: Apple purchase tokens linked to our account and purchase records, product and transaction identifiers, purchase and service-period dates, amounts and currency, tax country and tax amounts, and refunds. Reporting to Apple uses token-linked identifiers, not your card details. This is separate from push notification tokens.
  • Communications: messages you send us, including privacy requests and withdrawal notices, and our replies.
  • Technical data: IP address, browser and device information and request logs processed by our hosting providers, error reports, and server usage events linked to your account ID.
  • Website analytics, only with your consent: pages visited, clicks and feature use, session recordings with typed text masked and, when you are signed in, your account ID, name and email address.
  • Information about other people that appears in sources. Section 6 explains this.

4. Why we use your information and our legal basis

Processing based on legitimate interests must be necessary and balanced against your rights and reasonable expectations. You can ask how this applies to your data and object at any time (section 11).

Content safety checks can automatically stop a podcast request or an episode that breaks our rules. This does not have legal or similarly significant effects on you. If a check affects you, contact us and a person will review it. We make no other automated decisions about you.

  • Providing Podidex: creating and securing your account, generating, storing and playing episodes, syncing your library, sending the notifications and emails you turn on, running Live when you start it, applying usage limits and helping you with your account. Legal basis: performance of our contract with you (GDPR Article 6(1)(b)). Without this information we cannot provide the service.
  • Subscriptions and bookkeeping: taking payment, managing the purchased channel, handling withdrawals and refunds and keeping accounting records. Legal basis: performance of the purchase contract (Article 6(1)(b)); qualifying statutory accounting records are retained under the Swedish Bookkeeping Act (Article 6(1)(c)). iPhone Sandbox transactions do not charge real money.
  • Apple external-purchase reporting: reconciling token-linked transactions, renewals, refunds and corrections required by the applicable Apple external-purchase arrangement. Legal basis: our legitimate interest in operating that purchase channel and meeting its platform reporting requirements (Article 6(1)(f)), subject to necessity and balancing. Apple’s contractual reporting requirement is not itself a statutory bookkeeping obligation.
  • Security and abuse prevention: security checks at sign-in, rate limits, detecting misuse and automated content safety checks of podcast instructions and generated text. Legal basis: our legitimate interest in keeping Podidex and its users safe and meeting legal and app store requirements (Article 6(1)(f)).
  • Reliability: error reports, logs and server usage events used to find and fix faults. Legal basis: our legitimate interest in a working service.
  • Improving podcast quality: reviewing ratings, feedback and reports and copying selected episodes (idea, sources, script and feedback) into our internal test set to check that changes make episodes better. Legal basis: our legitimate interest in improving Podidex. If you object, we remove your episodes from the test set.
  • Website analytics and session recordings: understanding how our websites are used so we can improve them. Legal basis: your consent (Article 6(1)(a)), which you give and withdraw in Cookie settings.
  • Legal requirements and claims: complying with the law, answering authorities and establishing or defending legal claims. Legal basis: legal obligation or our legitimate interest.
  • Episodes that mention other people: see section 6.

5. AI generation and Live

When you create or schedule a podcast, your ideas, instructions, selected sources, relevant earlier episodes and podcast knowledge are sent to AI providers to research, plan and write the script. Search queries are sent to Tavily, and the script is sent to Google Gemini to produce speech. Instructions and generated text also go through OpenAI content safety checks.

Episodes are generated by AI and read by synthetic voices. They can contain errors.

When you join Live, your microphone audio, your listener name and the episode’s script, research and source text are sent through our relay to Google Gemini. Factual questions can be sent to Tavily for a web search, and the results to Gemini to form an answer. We do not record or store Live audio or transcripts. Search answers are deleted when the session closes; we keep session usage records. Google can keep conversation state for up to 24 hours so a dropped connection can resume. Leaving Live stops the microphone transmission immediately, but does not delete what has already been sent.

Do not include passwords, sensitive personal information or private information about other people in podcast ideas, instructions or Live.

6. People mentioned in sources

Podidex creates episodes from web pages, articles, papers, discussion threads and search results. These can contain personal information about people who do not use Podidex, such as authors, people in the news and commenters. We process the names, roles, statements and other information published in those sources.

We use relevant published information to produce factual episodes, with the legitimate interests of our users and us in access to information and expression weighed against the people concerned. Public availability is not unlimited permission. Source bodies are private processing material; listeners can read generated scripts and follow citations, not retrieve our stored articles or internal acquisition reports. Supported source uses, relevant knowledge and generated outputs have separate purposes and retention criteria.

This section provides public information for people mentioned in sources. Public availability of a source does not remove your rights. Any exception to individual notice must be justified in the particular circumstances; a lack of contact details alone is not enough. You do not need a Podidex account to exercise your rights: email privacy@podidex.com with the source address or episode reference. You can object, or ask us to correct or delete information about you. When we uphold a request, we stop using the source for new episodes and correct or remove the information we hold.

7. Who we share information with

We use the providers below to deliver and operate Podidex. Their roles depend on the service: for example, Stripe and Apple also use relevant information for their own payment, security or platform purposes. We may disclose data to authorities where the law requires it, and to a buyer if Podidex is sold, subject to applicable data protection rules.

  • Supabase: database, sign-in and audio file storage. All account and service data. EU (Frankfurt, Germany).
  • Google Cloud: runs podcast generation and our Live relay. Content needed for generation; Live audio in transit. EU (Belgium).
  • Vercel: hosts our website, web app and API. Data passing through the web app and API, including IP addresses. United States and a global network.
  • Expo EAS Update: delivers mobile app code and asset updates. IP address, operating system, app and update versions, and a randomly generated installation identifier. United States and a global delivery network. Update requests do not include your Podidex account, prompts or podcast content.
  • OpenRouter: routes AI text requests to model hosts such as Baseten, Together AI, Groq, Parasail, SiliconFlow and Wafer. Requests require endpoints offered as zero data retention; transient processing and operational metadata remain subject to the provider’s terms. Ideas, instructions, source text, scripts and podcast knowledge. United States and other countries where the model host operates.
  • Groq: fast AI text tasks such as episode titles. Podcast text. United States.
  • OpenAI: content safety checks and text embeddings for podcast knowledge. Instructions, generated text and extracted facts. United States.
  • Google Gemini API: speech generation, some text generation, Live conversations and Live search answers. Podcast text, scripts, voice instructions, Live audio and context and search results. Google’s global infrastructure, including the United States.
  • Tavily: web search for research and Live. Search queries and results. United States. We have disabled query-data use in our Tavily account. Tavily may pass queries to other search index providers to obtain results; do not include private information in search requests.
  • Source websites and services (for example Reddit, Hacker News and arXiv): fetch the sources you choose. The source address or search terms, not your account details. Various countries.
  • Cloudflare Turnstile: security check at sign-up and sign-in. Browser and device signals and IP address. Global. Cloudflare also uses these signals to improve its bot detection.
  • Mailgun (Sinch): sign-in codes, account emails, episode emails, purchase contract confirmations and withdrawal acknowledgments and internal notifications. Email address, podcast and episode titles and links, purchased plan, price, discount and contract/consent details, and the name, contract reference and message supplied in a withdrawal notice. EU.
  • Apple Push Notification service, Google Firebase Cloud Messaging and your browser’s push service: notifications you turn on. Device token, podcast and episode titles and identifiers. United States and global.
  • Apple external-purchase reporting: receives purchase-token-linked transaction identifiers, product, dates, amounts, currency, tax country and refunds to reconcile external purchases and calculate applicable platform fees. This is a separate recipient activity from Apple Push Notification service. Reports do not contain card details; Apple processes the reports under its applicable terms and privacy information.
  • Stripe: payments and subscription management for the website and the current test-only eligible iPhone external-purchase flow, with separate billing records. Name, email address, billing address, payment details and subscription information. EU (Ireland) and United States. Stripe is an independent controller for payment processing and fraud prevention under its own privacy policy.
  • PostHog: website analytics and session recordings (only with consent) and server logs and usage events. EU (Frankfurt, Germany).
  • Sentry: error monitoring. Error details and browser or device information. EU (Frankfurt, Germany).

8. Transfers outside the EU/EEA

Our main database is in the EU. Some recipients process data outside the EU/EEA. Documented arrangements for existing providers include incorporated data processing terms and Standard Contractual Clauses for Supabase and OpenRouter, and accepted data processing agreements for Sentry and PostHog. Applicable transfer routes include the EU-U.S. Data Privacy Framework where the recipient is certified and the activity is covered, or EU Standard Contractual Clauses with additional safeguards where needed. These are provider-specific arrangements, not a claim that every provider or new activity has the same coverage. Contact us for the relevant recipient’s transfer route and a copy of the applicable safeguards.

9. How long we keep information

  • Account, podcasts, scripts and settings: until you delete them or your account.
  • Episode audio on our servers: deleted automatically 30 days after the episode was created. The script and episode details remain. Downloads stay on your device until you or the app’s storage management remove them, or you delete the app.
  • Live: audio and transcripts are not stored. Search answers are deleted when the session closes. Session usage records are kept with your account.
  • Notification delivery records: 30 days. A per-episode record that prevents duplicate notifications is kept while the episode exists.
  • Private source copies: retained only while an assessed, supported use needs the specific source version, such as generation and its retries, factual knowledge extraction, source-grounded Live or an approved internal evaluation. A completed generation does not by itself justify indefinite storage. Copies shared by several supported uses can outlast one account; cleanup removes bodies after the last supported use ends, and upheld requests can restrict reuse or require scoped erasure.
  • Internal test set: selected material is retained only while its assessed evaluation purpose remains necessary and supported. Restrictions and upheld objections apply to separately held evaluation copies as well as operational sources.
  • Payment and accounting records: seven years after the end of the calendar year in which the financial year ended, as required by the Swedish Bookkeeping Act.
  • Checkout offers, purchase confirmations and immediate-start requests: as long as needed to establish what was agreed, resolve billing matters and handle legal claims. These records are separate from your app library and are not erased by account deletion.
  • Apple purchase tokens and reporting records: kept only as needed for the supported reporting, reconciliation, corrections, refunds and legal claims. Statutory accounting retention applies where a record qualifies as accounting information; it is not a blanket seven-year duty to keep every purchase token.
  • Support messages, privacy requests and withdrawal notices: as long as needed to handle the matter and any follow-up or legal claim.
  • Website analytics: session recordings 30 days and analytics events 1 year at PostHog. Error reports: 90 days at Sentry. Server logs: the logging provider’s standard retention, generally 30 days or less.
  • Backups are restricted recovery copies and rotate on the provider’s backup schedule. Deletion from active systems is not an immediate erasure from every backup, historical export or separately justified legal record; any retained copy remains subject to its applicable purpose and retention criteria.

10. Account deletion

Account deletion first cancels the website and iPhone-channel subscriptions owned by that account through their respective billing providers, then removes the sign-in account, podcasts, episodes, scripts, listening records, podcast knowledge and notification registrations. A billing cancellation failure prevents account deletion so a subscription is not left running. Server audio cleanup follows. Necessary payment, accounting, contract and Apple reporting records, independently supported shared sources, evaluation copies, support records, bounded diagnostics and recovery backups follow section 9; ask us about removal where applicable.

11. Your rights

You have the right to access your personal data and get a copy, to have it corrected, to have it deleted, to restrict its use and to receive data you gave us in a portable format. You can object at any time to processing based on our legitimate interests; we then stop unless we have compelling grounds that override yours or need the data for a legal claim. You can withdraw consent at any time in Cookie settings, without affecting earlier processing.

Email privacy@podidex.com to use your rights; Help & support explains how. We check that a request comes from the right person in a way that fits the request, and we never ask for your password or sign-in codes. We answer within one month. If a request is complex we may extend this by up to two more months, and we tell you within the first month. Requests are free.

You can complain to the Swedish Authority for Privacy Protection (IMY), www.imy.se, or to the data protection authority where you live or work.

12. Cookies and storage on your device

Our website and web app use only necessary cookies and local storage unless you accept more. Use Accept all, Reject optional or Manage preferences in the cookie banner. You can change your choice at any time under Cookie settings, which is linked at the bottom of our website and in the web app’s settings. One choice applies to both podidex.com and app.podidex.com.

The mobile apps contain no analytics or advertising SDKs and do not track you across apps or websites. They store your session, library cache, downloads and settings on your device so the app can work, including offline.

  • Necessary – podidex_consent: remembers your cookie choice. First party, 12 months.
  • Necessary – sign-in session (sb-* cookies and local storage): keeps you signed in. First party, until you sign out or the session expires.
  • Necessary – Cloudflare Turnstile: security check during sign-up and sign-in. Cloudflare, short-lived.
  • Necessary – podidex_claim: links a podcast you created on our website before signing up to your new account. First party, 30 days or until you sign up.
  • Necessary – web app cache (local storage, IndexedDB and service worker cache): loads your library quickly and offline. Stored per account. First party, until you clear site data.
  • Analytics, only with consent – PostHog (ph_* cookie and local storage): counts visits and feature use. First party, up to 12 months.
  • Session recordings, only with consent – PostHog: records page interactions with typed text masked. First party, same storage as Analytics.

13. Security

Data is encrypted in transit, and our database and storage providers encrypt stored data. Each account’s podcasts are separated by database access rules, audio files are private and shared through short-lived links, and only people who need access to operate Podidex have it. If a personal data breach puts your rights at risk, we will tell IMY and, where required, you.

14. Changes to this policy

We update this policy when our processing changes and show the date at the top. We tell you about material changes by email or in the app before they take effect.

Contact IMY