Privacy Policy

1. Who we are and what this covers

This policy is published by CocoReader ("we", "us"). It covers the CocoReader apps and this website (www.cocoreader.cc). We handle personal information in accordance with the Australian Privacy Act 1988 (Cth).

CocoReader uses accounts, product analytics, install attribution, crash reporting, and Apple subscriptions. Your books and generated audio stay on your device.

2. What we collect and why

We collect the following categories of information. We do not send book titles, authors, file names, book text, or generated audio to analytics, attribution, or crash reporting. We do not sell personal information.

Account. CocoReader uses Firebase Authentication. You can sign in with Apple, Google, or email. Firebase stores your email address and name (display name) when the sign-in provider provides them, plus a Firebase user ID. We use this to create and restore your account.

Product analytics. Mixpanel receives product events so we can understand onboarding, listening, and feature use. After sign-in, Mixpanel's distinct_id is your Firebase user ID. Events include onboarding answers (stored option IDs such as age range, gender, reading goal, and voice preferences — not button copy), app opens, books added or opened (no titles), listening sessions (duration, voice, engine; an anonymous on-device book ID, not the title or text), paywall outcomes, and coarse failure categories. Mixpanel does not receive book titles or book text.

Install attribution. AppsFlyer measures where installs come from and whether a trial or purchase followed. It receives install source and campaign, the Identifier for Vendor (IDFV), purchase events (trial start, subscribe, purchase), and a customer user ID equal to your Firebase user ID. The Identifier for Advertisers (IDFA) is collected only if you allow tracking in Apple's App Tracking Transparency prompt.

Crash reporting. Sentry receives crash reports and scrubbed diagnostic data (stack traces, release, environment) so we can fix bugs. When you are signed in, the Sentry user id is your Firebase user ID. Emails, names, book titles, and file paths are not set on the Sentry user and are redacted from messages.

Paywalls and subscriptions. Superwall is used for paywall display and subscription status. Subscriptions are purchased and managed through Apple. Apple processes payment. Prices, billing periods, and any trial are shown in the app and on the App Store at the time of purchase.

This website. The site uses Mixpanel for product analytics (page views and App Store button taps, including path, page title, referrer, and UTM parameters when present). Vercel hosts the site and may keep hosting logs. App Store buttons may use an AppsFlyer OneLink when one is configured.

3. Third parties

CocoReader uses these third-party services. Each processes data for the purpose listed here and keeps it under that provider's own policy.

• Firebase / Google — account sign-in (Apple, Google, or email). Email and name when provided by the sign-in method; Firebase user ID. Privacy policy.
• Mixpanel — product analytics in the apps (Firebase user ID as distinct_id, onboarding answers, listening and product events; no book titles or text) and on this website (page views and App Store taps). Privacy policy.
• AppsFlyer — install attribution. IDFA only with App Tracking Transparency consent; IDFV; install source; purchase events; customer user ID = Firebase user ID. Website App Store links may use AppsFlyer OneLink. Privacy policy.
• Sentry — crash reporting. Crashes and scrubbed diagnostics; Firebase user ID when signed in; no email, name, book titles, or file paths. Privacy policy.
• Superwall — paywall display and subscription status. Purchases are completed through Apple. Privacy policy.
• Apple — Sign in with Apple (name and email when you share them), App Store subscriptions and payments, and App Tracking Transparency. Privacy policy.
• Vercel — hosts this website and may keep hosting logs (for example request metadata) to operate the site. Privacy policy.

4. Tracking, ATT, and how to opt out

On iOS, CocoReader asks for tracking permission through Apple's App Tracking Transparency (ATT) prompt. That prompt is shown once, after the onboarding “finalising your plan” step, and only on the new-user onboarding path. The welcome Sign In path does not show it. Onboarding continues whether you allow or decline.

If you allow tracking, AppsFlyer may use IDFA for attribution. If you decline, the app still works. AppsFlyer may still receive IDFV, install source, purchase events, and your Firebase user ID as the customer user ID. Mixpanel and Sentry are not used to request IDFA.

There is no in-app toggle to turn analytics, attribution, or crash reporting off. You can:

• Decline ATT, or change it later in iOS Settings → Privacy & Security → Tracking (this controls IDFA).
• Ask us to delete your account and associated data via the contact page.

5. Books and audio stay on your device

Ebook files and generated audio are processed on your device. We do not upload your books or audio to CocoReader servers. Voice synthesis uses on-device resources. Mixpanel listening events do not include book titles or text — only things like duration, voice, engine, and an anonymous book ID created on the device.

6. How long we keep information

We keep personal information while your account is active, or for as long as we need it for the purpose described in this policy (for example analytics, attribution, crash reporting, or subscriptions). When we no longer need it, we delete it or anonymise it. Third parties keep data under their own policies, linked in section 3.

7. Account deletion and contact

To delete your account or ask a privacy question, use https://www.cocoreader.cc/contact. You can also email cocoreader+support@nammite.com. If you have a complaint about how we handle personal information, contact us first. You may also contact the Office of the Australian Information Commissioner.

8. Children

CocoReader does not knowingly collect personal information from children under 13. If you believe we have collected data from a child, contact us at https://www.cocoreader.cc/contact and we will delete it.

9. Changes

We may update this Privacy Policy from time to time. The date at the bottom will change when we do. Continued use of CocoReader after an update means you accept the revised policy.