App Privacy Policy

Last updated:

This is the policy for the Chukkāni mobile app. Looking for the website waitlist policy? To delete your account, see Account & data deletion.

Chukkāni is a storytelling app made for children, used by parents. This page tells you what we collect, why, where it goes, and what your rights are. The list is intentionally short.

1. Who runs the app

Chukkāni is operated by the Mana Katha team. If you want to reach us about anything in this policy, email customersupport@chukkani.com.

2. What we ask for at sign-up

When you sign up, we ask for one thing: a Google account or an Apple account. On Android you sign in with Google. On iPhone and iPad you can choose either Google or "Sign in with Apple".

You tap the sign-in button and your phone shows the standard chooser sheet. When you pick an account, the provider passes us a small amount of information about it:

  • With Google: your email address, the display name on the Google account, and the URL of the profile picture on the account, if you have one.
  • With Apple: your email address and your name. If you pick Apple's "Hide My Email" option, the address we receive is a private relay that Apple forwards from, not your real email. Apple sends your name only on the first sign-in, and Apple does not share a profile picture.

We use this to:

  • Recognise your account if you reinstall the app or switch phones.
  • Show which account is signed in on the Account screen.
  • Contact you about the account if something goes wrong. This is rare, and we will never email you for marketing.

We do not ask for your phone number, your home address, your date of birth, your payment card, your location, your contacts, your photos, or access to your microphone or camera. We do not ask for the child's real name. We do not request any extra scopes such as Calendar, Drive, Gmail, or contacts — only the basic profile shown on the chooser sheet.

If we ever add another sign-in method, such as email and password, we will update this policy before turning it on and ask you to agree again.

3. What you can choose to add later, inside the app

After sign-in the app lets you set up a child profile and pick reading preferences. These are optional and stay tied to your account:

  • A nickname for the child. You choose it, and it does not have to be the child's real name.
  • An avatar picture seed, which is a number that picks a cartoon avatar.
  • A default reading language and a country, used to show region-appropriate stories.
  • Reading preferences, meaning the themes and characters the child likes, picked during onboarding.
  • Reading history on this device, used to power "continue reading" and "for you" suggestions.

You can edit or clear any of this from the Account screen. Deleting your account (see section 8) removes all of it.

4. What gets stored where

  • On your phone, in the app's private storage: the nickname, the reading history, the language and country choices, the onboarding answers, and a flag recording that you accepted this policy and when.
  • In our cloud database (Google Firebase, hosted in India and the US): the account record (the email address and display name we received from Google or Apple, where an Apple email may be a private relay address; the account creation date; free vs. premium tier; and the date you accepted this policy) and the child profile (nickname, avatar seed, default language, country).
  • In Firebase Storage: the story files we serve to the app. These are our content, not your data.
  • If you subscribe, a small record of which devices use the subscription, so we can enforce a reasonable device limit. For each device we store an anonymous install identifier and the device model and OS version. This is used only to count devices against your plan, never for tracking or advertising.
  • If you tap the "Report" button on a story, the report you send — the story it refers to, your account ID, the reason you pick, and any note you type — so we can review the content. Please do not include personal information in the note.

We do not sell any of this. We do not share it with advertisers. There are no third-party ads inside the app.

5. Analytics

We use Firebase Analytics (Google) to count how many people open the app, which screens they look at, and whether features work. This is the only analytics tool we use. We do not use Mixpanel, Amplitude, Segment, or any marketing pixels.

Personal details are kept out of analytics events. The child's nickname is never sent as an analytics property. Your email address and display name are never sent as analytics properties. We send only an anonymous user ID (a random string Firebase assigns) so we can tell one device from another for counting.

Google may record the IP address of the device as part of Firebase's default behaviour. We do not store it ourselves or join it to your account.

We use Firebase Crashlytics (Google) to receive automatic crash and error reports so we can fix problems quickly. When the app crashes or hits an unexpected error, it sends the technical details of that crash — the error type, the stack trace, the device model, and the OS version — but not your name, your email, or the child's nickname. Crash reporting is switched off in debug builds and only runs in the released app.

6. Payments

If you subscribe to the premium tier, the purchase is handled by your phone's app store (Apple App Store or Google Play) and by RevenueCat, a third-party that helps us track subscription status. We never see your card number. RevenueCat receives an anonymous user ID from us so it can tell us whether your subscription is still active. It stores your purchase and subscription-status history keyed to that anonymous ID, and never receives your card details.

7. Notifications

The app sends a small number of notifications, for example "a new story is ready". Notifications are not used for marketing or re-engagement nudges. You can turn notifications off in your phone's settings at any time without losing access to anything in the app.

To deliver these notifications, the app registers a push token (an anonymous device-specific string from Apple or Google) and stores it with your account. It carries no personal information and is used only to send the notification to the right device.

8. Your rights

You can, at any time:

  • See what we have. Email us and we will send a copy of your account record and profile within 30 days.
  • Edit it. The Account screen lets you change the nickname, the language, and the country. To change which account is linked, sign out and sign in again with the account you want.
  • Delete the account. The "Delete Account" button on the Account screen deletes your sign-in from Firebase Auth, deletes the user record and all child profiles, and clears the on-device data. For a Google sign-in it also disconnects the app's access to your Google account. For "Sign in with Apple" it revokes Apple's token, so the app stops appearing under Settings → your name → Sign in with Apple on your Apple device. Reading history that only ever lived on the device is wiped when you delete the app. Once an account is deleted we cannot recover it.
  • Withdraw consent. If you no longer agree to this policy, delete the account. You cannot continue using a signed-in app without agreeing, because the account requires a Google or Apple sign-in.

For requests, email customersupport@chukkani.com from the email on the record so we can match the request to the right account.

9. Children

The app is designed for children to read, with a parent setting it up. We assume the person at sign-up is the parent or legal guardian. The Google or Apple account you sign in with is treated as the parent's, not the child's. We do not knowingly collect a child's real name, school, location, or photos.

We follow a COPPA-aware posture: no engagement-optimisation tracking, no name in analytics, no marketing notifications.

If you believe a child has signed up without a parent's permission, email us and we will delete the account.

10. Security

Data in Firebase is encrypted in transit (HTTPS) and at rest. Access to the database is restricted by Firebase Security Rules so that one account cannot read another account's profile or reading history. Firebase App Check is enabled to reduce abuse from outside the app.

No system is perfect. If we have a breach that affects your data, we will email the affected accounts within 72 hours of confirming it, and post a notice in the app.

11. Changes to this policy

If we change this policy in a way that matters, for example adding a new sign-in method, adding a new tracker, or sharing data with a new third party, the app will ask you to accept the new version the next time you sign in. Editorial fixes will not trigger a re-prompt, but the "Last updated" date at the top will change so you can see when the page was touched.

12. Jurisdiction

We operate from India. By using the app you agree that disputes about this policy will be handled under Indian law, in the courts of Hyderabad.


By tapping "I agree" on the sign-in screen, you confirm you have read this policy and consent to us collecting and using your Google or Apple account information, profile information, and analytics data as described above.