MVP beta privacy

Private personalized audio should stay private.

Chroncast is in MVP beta. This policy summarizes the product's current data posture so early listeners know what the app collects, why it is used, how subscription billing works, and how to delete it.

What we collect

• Account basics such as name, email, password hash, and mobile bearer tokens.
• Podcast preferences from onboarding: topics, tone, length, delivery time, timezone, voice, delivery channel, optional delivery destination, and optional US ZIP code when you ask for local weather.
• Trusted source preferences such as topic-search prompts and public RSS or site URLs you provide.
• Generated episode data: plans, scripts, private audio files, delivery attempts, in-app notifications, and listener feedback.
• Subscription and billing metadata such as plan, billing provider, product ID, transaction or subscription ID, trial dates, renewal status, cancellation status, and limited payment-provider customer IDs.
• Beta signup email, optional name, and optional topic hints when you request access from the landing page.

Payment information

Chroncast does not collect or store full credit card numbers, card security codes, or complete app-store payment credentials. In-app subscriptions on iOS are processed by Apple. In-app subscriptions on Android are processed by Google Play. Web or non-mobile subscriptions may be processed by Stripe. Chroncast stores the billing metadata needed to confirm access, troubleshoot subscriptions, prevent duplicate entitlements, and support cancellation or account deletion.

What we do not collect in the MVP

Chroncast does not connect to your email, calendar, health data, social accounts, or other personal connectors in the current MVP. Source collection is limited to your selected topics and public trusted RSS or site sources.

How the data is used

We use your preferences and feedback to generate, render, deliver, and improve your private daily podcast. When configured, Chroncast sends episode plans, source snippets, scripts, and voice-rendering requests to OpenAI so it can draft scripts and generate speech audio. If you provide a ZIP code with weather-sensitive topics, Chroncast uses Open-Meteo geocoding and forecast APIs to turn that ZIP into local weather snippets for the episode plan. Admin exports and dashboards are protected by the MVP admin access gate and are intended for beta operations and debugging.

Deletion and retention

The mobile app includes a delete-account action that requires typing DELETE before submission. When confirmed, Chroncast deactivates the account immediately, deletes the listener profile including any saved ZIP code, source preferences, generated episodes, delivery attempts, feedback, notifications, API tokens, rendered audio artifacts, and any beta signup row matching the account email. The account record remains soft-deleted for 10 days before permanent hard deletion.

Production providers

OpenAI is the current configurable provider for production-style script drafting and speech audio. Open-Meteo is used for optional ZIP-based local weather snippets when weather-sensitive topics are selected. Apple, Google Play, and Stripe may process subscription purchases depending on where you subscribe. SMS and external source-search providers have not been finalized. Before launch, this page should be updated with any additional provider-specific processing details and legal terms required for public beta.

Contact

Questions about privacy, billing metadata, or account deletion can be raised through the Chroncast beta support channel provided with your invitation.

Last updated: May 28, 2026.