Children's Privacy

What we know about a child

For each kid using Kuros Lab in a classroom, the app holds:

• A nickname the teacher entered (e.g. “Mina K.”).
• A grade or class group the teacher chose.
• Their answers on activities — which step order they chose, which option they tapped, how long it took.

That's the complete list. No email. No last name (unless the teacher chose to include it). No date of birth. No photo.

What we never collect from kids

• Email address, phone number, home address, school address
• Photos, videos, or audio recordings
• Precise GPS or location data
• Advertising IDs (the app contains no ads, so we have no use for them)
• Browser history, cross-app behavior, or social-media activity
• Biometric data (fingerprints, face data)
• Contacts, calendar, or any device data beyond what's strictly needed to run the app

This isn't a “we may collect, but only if necessary” list. It's a “we technically cannot, by design” list — the app doesn't request the permissions that would make any of this possible.

How a child gets in

Kids do not create accounts. They open the app, enter a six-character class code their teacher gave them, and join the mission. There is no password, no email verification, no identity check that would link the kid to anything outside the classroom.

Class codes are issued by the teacher and can be rotated or revoked at any time from the teacher dashboard. A revoked code immediately removes that kid's ability to access the app and the kid's identity from our system.

No ads, no in-app purchases, no chat

• No advertising in any part of the app — kid mode or adult mode. We do not run an ad business and we don't integrate ad SDKs.
• No in-app purchases visible to kids. Teachers may have paid plans (handled outside the kid flow), but a kid will never see a buy button or a paywall.
• No social or chat features exposed to kids. Kids cannot message each other, post publicly, or interact with anyone outside their class.
• No external links in kid mode. Kids cannot navigate to third-party websites from inside the app.

Third-party SDKs

Google Play's Families Policy requires that any SDK in a child-directed app be on the approved list. Our policy is stricter: we use only SDKs that ship with no telemetry by default.

If we ever add an SDK that processes any kid data, we'll update this table at least 30 days before it ships and notify signed-in teachers by email.

Parental consent & teacher control

In a US classroom, COPPA permits a school or teacher to consent on behalf of a parent for educational use. Kuros Lab is designed for this model: the teacher chooses to use the app in their classroom, hands out class codes, and is responsible for parent communication about their classroom tools.

For families using Kuros Lab outside a classroom (homeschool, after-school, parent-led learning), the parent or guardian acts as the “teacher” — they create the adult account, issue the class code to their own child, and remain in control.

How to remove a child

Three paths, in order of speed:

• Teacher dashboard — the fastest. Open the class, tap the kid's row, tap “Remove.” Their nickname and all attempts are deleted immediately.
• Teacher revokes the class code — disconnects all kids in the class from the app. They can no longer rejoin without a new code.
• Email us at privacy@kuroslab.com from a parent or guardian email — we'll locate the records (you'll need the class code or teacher email) and delete them within 14 days.