Privacy Policy
FamzoLearn · last updated 15 October 2026
The short version
- Your child’s age band never leaves the phone. The nickname you choose — never a real name — is shared only with the other grown-ups in your family, and with families you have invited into your child’s friends circle.
- There are no analytics and no third-party tracking in this app, and the current version shows no advertising. If that ever changes, we will update this policy and tell you in the app before it takes effect. If the app crashes, a crash report (the error, the device model and the app version, no name or account) goes to Google so we can fix it.
- FamzoLearn is used through a parent’s account. In the cloud we hold the parent’s sign-in email and the child’s learning progress — chapters read, streaks, difficulty level — against a random account number, not a name.
- The stories and cards are read by recordings we made in advance. When your child presses play, the app asks our server for that one recording; the request carries the random account number and which chapter or card — not the age band, not a name.
- All of this is true of the web version at famzolearn.com/app too — same account, same rules. The three differences a browser forces are named below.
- We never sell or share personal data. There is nobody to share it with.
- If you subscribe on this website rather than through Apple or Google, our payment processor takes the payment. We still never see your card.
- To have everything deleted, email privacy@famzolearn.com. We action it within 30 days.
Who we are
FamzoLearn (“we”) is operated by Nostomic Technologies LLP, a limited liability partnership registered in India, and makes a learning service for families: the account belongs to a parent, and children of about 2 to 8 use it with them. For data-protection purposes we are the controller (UK/EU GDPR) and the Data Fiduciary (India’s DPDP Act) for the data described below. You can reach us at privacy@famzolearn.com.
This policy covers all three places you can meet us: the mobile apps for iPhone and Android, the web app that runs in a browser at famzolearn.com/app, and the rest of this website. The web app is the same product signed in to the same account — a browser simply has different plumbing, and where that changes something it is called out below rather than left for you to work out.
What stays on the device
The following is written to storage on the phone or tablet and is never transmitted to us. It is removed when the app is deleted.
| What | Why |
|---|---|
| Age band (2–5 or 5–8) | To pick story length and difficulty. |
| The parent’s email as typed at set-up | Kept locally so the app remembers who set it up. It is also used to create the sign-in account — see below. |
| Reading theme, reminder times, cached lessons | Preferences and offline use. |
The same thing, in a browser
The web app writes exactly this list to your browser’s own local storage, under the same names, on your own machine. It is not a tracking cookie, it is not read by anyone else, and it is never transmitted to us. Firebase also stores your sign-in token there so you are not asked to log in on every visit.
Clearing site data for famzolearn.com in your browser removes all of it, exactly as deleting the app does on a phone. Using a private or incognito window means it is discarded when you close the window.
What is sent, and to whom
We use Google Firebase, and nothing else, as our back end. Google processes this data on our instructions.
| What | Where | Why |
|---|---|---|
| Parent’s sign-in: email address and password, or the email (and, if you allow it, the name) Google or Apple passes us | Firebase Authentication | So the account can be signed in to, on the phone and on the web. A password is stored hashed by Google; we never see it. Before a parent signs in the app holds only a temporary anonymous session, used for the short free sample a guest can try (a few chapters and cards); nothing about the family is kept against it. |
| Learning progress — chapters read, streak count, difficulty level, which daily items are done | Cloud Firestore | So progress survives reinstalling. It is stored against the random account identifier, not against your child’s name or age. |
| The child’s nickname | Cloud Firestore | So every grown-up in the family sees the same name, and a rename on one phone reaches the other. We ask for a nickname rather than a real name on purpose, and the app says so where it asks. Stored against the random identifier, and readable only by the grown-ups in that child’s family. |
| Family: each grown-up’s sign-in email and display name | Cloud Firestore | Only when a second parent joins. So each of you can see who else is in the family and remove them. Nobody outside the family can read it. |
| Friends circle: the child’s nickname, an avatar colour, streak count and the last day they learned something; invite codes | Cloud Firestore | Only if you invite another family, or accept their invite. That family can see these four things and nothing else — no messaging, no photos, no location. Leaving the circle or deleting the account removes them. |
| Requests for lesson pictures | Firebase Storage | Downloading illustrations. Read-only — the app never uploads anything. |
| Requests to play a recording: the random account number and which chapter or card | Cloud Functions (Mumbai, India) | So the app can play the narration. The server checks the request comes from a signed-in copy of the app and answers with a link to that one recording that stops working after 24 hours. The child’s age band is not sent: every version of the recording comes back and the phone picks its own. For requests that cannot show they come from our genuine app, the account number and chapter are written to our server log so we can spot someone copying the library; that log is deleted after 30 days. |
| Crash reports, only if the app crashes: the error and where in the code it happened, the device model, operating system and app version | Firebase Crashlytics | So we can find and fix what broke. No name, email, nickname or account number is attached. Google keeps crash reports for 90 days. |
| A proof that a request comes from the genuine app | Firebase App Check, using Google Play Integrity (Android), Apple App Attest (iPhone) or, in the web app, Google reCAPTCHA Enterprise | So the stories and recordings can only be fetched by the real FamzoLearn app, not by a script copying the library. Play Integrity and App Attest check that the app and device are genuine; they receive nothing about your child. In the web app, reCAPTCHA Enterprise does the same job: it looks at information about the browser and device (for example, which browser it is and how it is set up) and at how the page is being used (for example, mouse, touch and keyboard activity), to tell a real person using the web app from an automated script. Like any request, it also carries your browser’s IP address. There is no puzzle and no checkbox. It runs only inside famzolearn.com/app, from the moment the web app is opened, and never on our other pages. It is a security check and nothing more: Google processes it for us, it is not used for advertising, and it is not used to build a profile of you or your child. We rely on our legitimate interest in keeping the service secure (see why we are allowed to hold it). |
| Whether a subscription is active, and when it expires | Cloud Firestore | So the app knows whether to show today’s content. Held against the same random account identifier. No card number, no billing address, no payment history. |
Security rules on our database restrict every progress record to the single account that created it. One family cannot read another’s.
The web app talks to the same Firebase project, over the same rules, with the same account. Nothing about it is a separate database and nothing extra is collected because you happen to be in a browser. Your browser sends its IP address and user-agent to Google when it makes those requests, as it must for any request to reach a server at all; Google holds those in its own operational logs under its privacy terms. We do not read them, keep them, or use them to work out where you are.
If you open your browser’s network inspector on the web app you will see these
hosts: identitytoolkit.googleapis.com (signing in),
firestore.googleapis.com (the progress and the lessons),
asia-south1-curiokids-2a662.cloudfunctions.net (asking for a recording),
storage.googleapis.com (the pictures and the recordings themselves), and
three that belong to the genuine-app check described above:
www.google.com/recaptcha and www.gstatic.com/recaptcha (Google’s
reCAPTCHA code; occasionally recaptcha.google.com instead) and
content-firebaseappcheck.googleapis.com (turning the check’s result into a
pass our server accepts). You may also see a request to
www.google.com/images/cleardot.gif — that is Google’s own
connection check inside the Firebase library, a one-pixel image with no content, and we
neither add it nor see its result. We would rather name it here than have you find it
and wonder. The Firebase code itself is served from famzolearn.com, not from
Google’s CDN. There are two exceptions. One is the reCAPTCHA check: it is Google’s own code,
loaded from Google as soon as the web app opens — before anyone signs in, including
for a guest trying the free sample — and only inside the web app. The other is Cashfree’s payment code (sdk.cashfree.com and other cashfree.com addresses), which loads only when a parent in India chooses a plan, to take the payment.
What we never collect
- Advertising identifiers
- Location
- Camera, microphone or photos
- Contacts
- Analytics or usage tracking
- Behavioural profiles
- Voice recordings
- Biometrics
Stories and cards are read by recordings we produced in advance with professional text-to-speech voices (ElevenLabs and Google). They are made once, in our own studio, from our own scripts — no family’s data is ever sent to those services. If a recording cannot be reached, the device’s own built-in speech (or, in the web app, the browser’s) reads instead, on the device. Either way nothing your child says is recorded, and the microphone is never asked for. Reminders are generated on the device; we do not operate push notifications.
Payments and subscriptions
The app is free to download and includes a free trial. There are two ways to subscribe, and they are handled by different people.
Bought inside the app
The purchase is handled entirely by Apple or Google under their own terms. We never see or store your card details. What we receive back from the store is whether a subscription is active and when it expires, held against the same random account identifier as your progress.
Your country for pricing and trial length is read from your App Store or Google Play storefront — the country your account is billed in. We do not use your IP address or your device location to work out where you are.
Bought on this website
The payment is taken by Cashfree Payments, an RBI-authorised payment aggregator acting on our behalf. You enter your card details on their page, not ours, and they never reach our servers — we still never see or store a card number. To set up the auto-pay mandate (UPI Autopay, card or bank) they also need your mobile number: you type it on our subscription page, we pass it straight to them, and we do not keep it. They hold your name, email address, mobile number, billing country and the payment record as their own controller, under their privacy policy and under the card-network rules they are bound by; we receive back only the fact that a payment succeeded, the plan you bought, and when it renews.
We keep an invoice for each website purchase — your name, email address, billing country, the amount and the tax — because Indian tax law requires us to. That is the one record here that survives a deletion request, and only for as long as the law says. It is not linked to anything your child did in the app.
For a website purchase, the country used for pricing is the billing country you enter yourself. We do not geolocate you.
Children, and how a parent consents
This app is for children, so a parent or guardian sets it up and consents on the child’s behalf. A guest can try a short free sample (a few chapters and cards) first; everything else waits until a parent signs in with Google, Apple or an email address; the sign-in and set-up screens show these terms and this policy, and ask the person continuing to confirm they are the child’s parent or legal guardian and an adult. We do not ask for the child’s real name or date of birth: the parent chooses a nickname and one of two age bands (2–5 or 5–8), and the age band stays on the device.
India’s Digital Personal Data Protection Rules, 2025 require, from May 2027, that the parent giving consent is verified as an identifiable adult. Before then we will add that verification (for example through a DigiLocker age token) and update this section.
Different countries define a child differently, and we apply the strictest rule that applies to you:
- India — under the DPDP Act a child is anyone under 18. Every user of this app is a child under that definition.
- United States — COPPA covers children under 13.
- UK and EU — the age at which a child can consent for themselves is between 13 and 16 depending on the country. Again, every user of this app is below it.
We do not profile children, we never use a child’s data for targeted or personalised advertising, and we do not use their data to decide what to sell them.
Why we are allowed to hold it
In the UK and EU we rely on consent given by the holder of parental responsibility (GDPR Art. 6(1)(a) and Art. 8), on the necessity of processing to perform the contract where you have bought a subscription, and on our legitimate interest in keeping the service working and secure. In India we rely on the verifiable consent of the parent. You can withdraw consent at any time by asking us to delete the account.
How long we keep it
This is our written retention policy. Nothing is kept indefinitely.
| What | Kept for |
|---|---|
| Learning progress, streaks, the nickname, family and friends-circle entries | Until you delete the account, or 24 months without use, whichever comes first |
| The parent’s sign-in email | The same |
| Subscription status (active / expires on) | The same |
| Server log of recording requests from unverified apps | 30 days |
| Backups | Cleared within 90 days of a deletion |
| Invoice for a website purchase | 8 years, because Indian tax law requires it — the invoice only, not the account |
| Anything on the device | Until the app is deleted |
Deleting everything
In the app: Parent Corner → Account → Delete account removes the account and everything held against it straight away. Or email privacy@famzolearn.com from the address the account was created with and we will delete the account and all associated progress within 30 days, then confirm. Deleting the app from the device removes everything held locally straight away.
Who handles data for us
Only these, and only for the purposes named:
- Google (Firebase and Google Cloud) — sign-in, database, file storage, our server functions, crash reports (Crashlytics) and genuine-app checks (App Check with Play Integrity on Android, and with reCAPTCHA Enterprise in the web app), as our processor under Google’s data-processing terms, which include its security commitments.
- Apple and Google — in-app purchases, and “Sign in with Apple” / “Sign in with Google” if you choose them (they pass us your email address and, if you allow it, your name), as their own controllers.
- Cashfree Payments — website purchases, as its own controller.
- Apple — App Attest, which confirms to us that a request comes from the genuine iPhone app. It carries no information about you or your child.
No one else receives any data about you or your child: no advertisers, no analytics companies, no data brokers, and no one training AI models.
We keep a written information-security programme: who can reach the data, the safeguards (for example, database rules that keep every family’s records to that family, and recordings that can only be fetched through the app), and a review at least once a year.
Where the data goes
Google’s Firebase infrastructure may process data outside your country. For transfers out of the UK or EEA we rely on the Standard Contractual Clauses in Google’s data processing terms. For India, transfers are made only to countries not restricted by the Government under the DPDP Act.
Your rights
Depending on where you live you may ask us to give you a copy of the data, correct it, delete it, restrict what we do with it, or object to it. In India you may also nominate someone to exercise these rights on your behalf. Write to privacy@famzolearn.com.
If you are unhappy with our answer you can complain to your data protection regulator — the ICO in the UK, your national authority in the EU, or the Data Protection Board in India.
This website
The public pages — the home page, the pricing page, this one — set no cookies, run no analytics and embed nothing from anyone else. No tag manager, no pixel, no font from someone else’s server. The example photographs are served from our own storage. If you email us, we keep that email so we can reply to it.
Two pages are necessarily different, and both only after you choose to use them:
- The web app at famzolearn.com/app keeps your sign-in token and your
child’s local settings in your browser’s local storage, as described above.
That is strictly necessary to keep you signed in; it is not used to track you and there
is nothing to opt into. Once the web app is open, Google reCAPTCHA (the genuine-app check
described above) also sets one cookie,
_GRECAPTCHA, on google.com. It is strictly necessary for that security check and is used for nothing else — not advertising, not measurement — and none of our other pages sets it. - The checkout hands you to Cashfree Payments, who will set whatever their own payment and fraud-prevention flow requires. That is their page and their policy; we do not place anything of our own on it.
We do not use cookies for advertising or measurement anywhere, on any page, so there is no consent banner to dismiss.
Changes
If we change how any of this works we will update this page and change the date at the top. If a change is significant we will tell you in the app, in the web app, and by email before it takes effect.
Contact
The Terms of Service sit alongside this policy and cover what you may do with the app, what a subscription costs and how to get a refund.
Privacy: privacy@famzolearn.com
Anything else: support@famzolearn.com