Privacy notice

Your place in the story belongs to you.

This notice explains the information Then What? uses across the website and mobile apps, why we use it, and the controls available to you. Last updated October 14, 2026.

Playback and product activity

We record what you watched, saved or followed, how far you got, playback performance, app interactions, and diagnostic events. We use this information to keep your place, make features work, measure engagement, and diagnose failures. Our session-recording provider, LogRocket, records website and app sessions, which may include taps, scrolling, screen and page layout, app errors, and performance timings. Typed form values, email addresses, sign-in codes, and payment and purchase panels are excluded. App recordings are linked to a one-way code derived from your viewer identifier, not to your name or email address, and are not used to track you across other companies' apps or websites. On Android, turning measurement off in Account also stops app session recording. In the European Economic Area, the United Kingdom, and Switzerland, the app records sessions only if you allow measurement in Account.

Mobile app and device identifiers

Each app installation receives a random installation identifier. On iPhone and iPad we may also collect Apple's identifier for vendor (IDFV). On Android we use Google Play Install Referrer for supported install attribution. We do not request Apple's App Tracking Transparency permission and do not collect IDFA, Android advertising ID, IMEI, or fingerprint your device.

Attribution and AppsFlyer

On Android, when measurement is on, we use AppsFlyer to understand how an installation reached Then What? and whether campaigns lead to viewing or purchases. Measurement is on by default, and you can turn it off at any time in the app under Account, Promotion measurement. In the European Economic Area, the United Kingdom, and Switzerland it stays off unless you allow it. AppsFlyer may process its installation identifier, Google Play Install Referrer details, app and device information, IP-derived network information, and selected in-app events, and may report installs and those events to advertising platforms such as Meta so we can measure and improve our campaigns. On iPhone and iPad, we use IDFV for first-party app functionality and analytics; the iOS app does not include AppsFlyer, and we do not share IDFV with it. We do not send your email address, title searches, dialogue, or free-form text to AppsFlyer. Partner postbacks are limited to approved events and settings.

Accounts and linkage

If you sign in, we use your email address to verify and secure your account and to link activity across devices, including saved series, playback progress, purchases, and subscription access. Without sign-in, activity is associated with a random browser cookie or app installation identifier instead.

Purchases

Payments are processed by Stripe on the web and by the App Store or Google Play in the mobile apps. We receive purchase, subscription, entitlement, product, transaction, and refund information needed to unlock content, restore purchases, prevent fraud, provide support, and keep financial records. We do not receive full card details from these providers.

Notifications and email

If you allow push notifications, we store a push notification token and its delivery status so we can send the notifications you enabled. You can change permission in device settings. If you follow a series or opt into announcements by email, we use your confirmed address for those choices. Every marketing email has an immediate unsubscribe link.

Public community comments

With authorization from our account operators, we use the YouTube, Instagram and Facebook APIs to read public comments and their reply threads on our own accounts and publish replies as Then What?. We send relevant public comment text and thread history, together with the corresponding episode captions and story context, to OpenAI to prepare and check replies. We keep reply records to avoid duplicates and handle follow-ups. Private messages and payment credentials are excluded from this workflow. Account authorization credentials are encrypted and are not sent to the language model. Operators can revoke access through the connected platform. Contact us using the privacy-request details below for questions about these records.

Service providers and disclosure

We use service providers to host the service, store data and media, deliver email and push notifications, process payments, diagnose app behavior, and measure attribution. They process information for those purposes under their own contractual and security obligations. We may also disclose information when required by law, to protect people or the service, or as part of a corporate transaction. We do not sell personal information.

Retention, security, and your choices

We retain information for as long as needed for the purposes above, then delete or de-identify it, subject to legal, accounting, fraud-prevention, backup, and dispute requirements. Access is restricted and sensitive identifiers are encrypted or hashed where appropriate. No system is completely secure.

You can unsubscribe from email, disable push notifications, clear browser data, or delete your account. For access, correction, deletion, or another privacy request, [email protected]. We may verify your identity before fulfilling a request.

Age requirement and changes

Then What? is intended for adults 18 and older and is not directed to anyone under 18. We do not knowingly collect information from anyone under 18. If we learn that someone under 18 has given us information, we will delete it. If you believe a minor has provided us information, contact us at [email protected] so we can remove it.

We may update this notice as the service changes; material changes will be reflected here with a revised date.