Privacy & child safety
The users are children.
That is a design constraint before it is a legal one. These are the rules we build to.
Principles
Six rules, in plain language.
Written for a parent or a principal to read in two minutes, not for a lawyer to hide behind.
The public demo collects nothing
Memory Missions and the chapter demo run entirely in your browser. Your answers stay in the tab's session storage and are gone when you close it. No account, no cookie banner because there is nothing to consent to.
No child's name in the demo
Nothing on this site asks a child who they are. Inside a school, students appear to teachers by roll number, and student-level data is never shown outside that school.
Only what the product needs
Answers, confidence, and timing on concepts a school has chosen to track. That is what makes retrieval scheduling work. We do not collect location, contacts, device identifiers or browsing behaviour.
No diagnosis, ever
MonsoonSafe reports what happened to an answer — faded, crossed wires, a missing earlier step. It never states or implies that a child has ADHD, dyslexia, or any psychological or medical condition. Those are clinical judgements, and a learning product has no business making them.
No advertising, no data sale
There is no ad product. Child data is never sold, brokered, or used to target anything. The school pays for the software; that is the whole business model.
The school stays in control
The school decides which classes participate and which chapters are tracked, and can ask for its data to be exported or deleted.
Enquiries
School contact details are the one thing we do collect.
The Founding School form asks an adult decision-maker for their name, role, email and school. We use it to reply about a pilot, and nothing else.
This page describes the product principles the MVP is built to. It is not yet a full legal privacy notice; a complete notice will accompany the first school deployment, alongside the data-processing terms a school signs.