There is no setting to share a child’s data.
Not because it’s switched off — because the screen to turn it on does not exist. A child’s conversations with the tutor never leave the device. This is not a policy we promise to follow; it is how the system is built.
“Every conversation stays on this device — no one else can read it. Not even us.”What a child reads in their own conversation history
The covenant
Six commitments, enforced in code.
Each of these is checked automatically on every build of the product. A change that breaks one fails before it can reach a child.
Conversations never leave the device
The data format that syncs to school has no field that can hold conversation text. There is nothing to leak, subpoena or sell, because there is no server that has it.
Only a fixed whitelist crosses
Mastery levels per concept, misconception codes, session outcomes and similar — every field an ID, a category or a bounded number. Outcomes cross; the process behind them never does.
Consent is per child
Nothing leaves a device for a learner without their guardian’s active consent. One sibling’s consent never covers another, and consent can be withdrawn.
No AI in the cloud, no trackers on the phone
Speech, reasoning and the tutor’s voice all run on the device. The student app contains no analytics SDKs and sends no remote logs of what a child does.
A child’s secret stays theirs
The PIN or picture story a child uses to sign in is stored in protected form on the device, never synced and never logged. Children are never asked for biometrics.
No dark patterns
Nothing rewards screen time. Streaks pause instead of shaming, there is no guilt copy, and a child never sees the words “wrong”, “failed” or “locked”.
Exactly what moves
What crosses the wire, and what never does.
Crosses — with guardian consent, as IDs and numbers
- Mastery level for each concept
- Misconception codes, such as “soil is food”
- Star events and session outcomes
- Counts of language use and question types — never the words
- A safety flag’s category only, so a teacher can check in
- Device-signed credentials, for the school to endorse
Class views aggregate groups of at least five children, so no individual can be singled out.
Never crosses — for anyone
- What a child said or asked
- Where a child hesitated, or how long they took
- Recordings of a child’s voice
- Photos of homework
- A child’s sign-in secret
- Anything about attention or behaviour
Not encrypted-and-sent. Never sent.
India’s DPDP Act
Designed for the law, then built stricter.
The Digital Personal Data Protection Act and its Rules require verifiable parental consent for children’s data. We treat that as the floor. Where the law permits more, we built less — because the safest data is data that was never collected.
Your rights, and who to ask
Guardians can withdraw consent for a child at any time through the school; from then on, that child’s phone syncs nothing about them. For any question or grievance about personal data, write to our Grievance Officer.
- Grievance Officer (DPDP Act)santosh@enumora.in
- Registered officeEnumora Technologies Private Limited, Hawelia Valenova Park, Techzone-IV, Greater Noida, Uttar Pradesh 201318
This page describes how the Enumora product handles children’s data. For this website, see the website privacy notice.
Test it yourself.
Ask us for a demonstration, then switch off the Wi-Fi and inspect what the phone sends when it reconnects.