Privacy Policy

KinderGlow is used by a parent on behalf of a young child. This page sets out exactly what the app collects, why, where it is stored, and how to have it removed.

Effective date: 29 July 2026  ·  Applies to: the KinderGlow Android app (com.kinderglow.app) during internal testing, and this website.

What we collect

Parent account

You sign in with Google. We receive and store the email address associated with that Google account, together with an internal account identifier and the date the account was created. We do not receive your Google password. Sign-in is handled by Supabase Auth (see Third-party services).

Child profile

When you set up a child profile, you provide:

• a name for the child — a first name or a nickname is fine, and we do not ask for a surname;
• the child's age in years;
• the child's board and class (for example ICSE, Senior KG), which selects the curriculum content.

We do not ask for the child's date of birth, photograph, address, school name, or any contact details for the child.

Learning progress

So the child can continue where they left off and so you can see how they are getting on, we record activity results against the child profile: which activities and skills were attempted, an accuracy score, whether a skill is marked as mastered, stars earned, day and streak counters, and the timestamps of practice sessions.

Device and operational data

The app registers the device it is running on so that you can see and revoke the devices signed in to your account. We store the platform (Android or iOS), the device model reported by the operating system, a device label, an identifier generated by the app, and when the device was last seen.

Our servers keep ordinary request logs — timestamp, the route that was called, response status and timing. These logs are built to exclude your account identifier, your child's identifier and any personal data: the server records the route pattern rather than the address actually requested, precisely so that an identifier in a web address never reaches a log file. They are operational records used to diagnose faults, and are not used to build a profile of you or your child.

Microphone and voice

When voice input is enabled in a future release, it works as follows, and this is enforced in the app's code rather than by policy alone:

• Speech is recognised by your device's own on-device recogniser. The app explicitly requests offline recognition and will not fall back to a network recogniser.
• If your device has no on-device speech model available, KinderGlow disables voice input rather than sending audio anywhere.
• KinderGlow does not record, store, upload or transmit audio. Only the recognised text is used, on the device, to check the child's answer.
• Android may download a speech-recognition language model from Google in order to make on-device recognition available. That is a download to your device; no audio is uploaded as part of it.

Speech recognition itself is provided by your device's operating system and is governed by your device manufacturer's and Google's terms.

Where data is stored

Data is transmitted over HTTPS. The release build of the app is configured so that it cannot make unencrypted connections.

Third-party services

A payments library is present in the app package but is inactive: no payment method can be added, no purchase can be made, and we collect no payment or card information. There are no paid features during internal testing.

What we do not do

• We do not show advertising, and we do not use advertising identifiers.
• We do not include third-party analytics, attribution or crash-reporting SDKs.
• We do not sell, rent or share personal data with third parties for their own purposes.
• We do not track your child across other apps or websites.
• We do not collect precise location.
• We do not collect contacts, photos, files or the device's advertising ID.

Retention and deletion

Account, child profile and progress data is kept for as long as your account exists, because its purpose is to keep the child's learning continuous across reinstalls and devices. Operational server logs are kept for a limited period for fault diagnosis and then age out.

You can ask us to delete a child profile or your entire account at any time by emailing support@kinderglow.in from the address you signed in with. Deleting an account removes the child profiles, sessions and progress attached to it. We will confirm once this is done.

You may also ask us what data we hold about your account, and ask us to correct it, using the same address.

Children's privacy

KinderGlow is intended for children aged roughly 3 to 6, used together with a parent or guardian. The account belongs to the parent. Everything we hold about a child is either entered by the parent — a name or nickname, an age, a class — or generated by the child's use of the learning activities.

We do not knowingly collect contact details from a child, we do not enable a child to communicate with anyone through the app, and there is no user-generated content, chat, or social feature.

Changes to this policy

KinderGlow is in active development, and this policy will change as features are added — particularly when voice input is enabled and when paid features are introduced. The effective date at the top of this page reflects the current version, and material changes will be communicated to testers before they take effect.

Contact

Questions about this policy, or requests relating to your data:
support@kinderglow.in