Security & incident response
Version 2026-10-16 ยท Effective 16 October 2026. How we protect your family's data and what we do if something goes wrong.
1. How data is protected
- All traffic is encrypted in transit (HTTPS) and data is encrypted at rest by our hosting provider.
- Every family's data is isolated at the database level: a signed-in parent can only ever read or change their own family's rows, enforced by the database itself, not just by the app.
- Child sign-in codes are stored only in scrambled (hashed) form โ we never store the actual code.
- Five wrong child codes in 15 minutes temporarily lock that child's sign-in.
- New devices must be approved by the parent by email before any child can use them.
- Security-related events (sign-ins, wrong-code attempts, device approvals, admin actions) are recorded in an audit log kept for 24 months.
- The administrative area is restricted to the site owner only, and every administrative action is logged.
- Staff access is limited to the owner of ASM Professional Services.
2. Payments
Card payments are handled entirely by Stripe. We never see or store your full card number. Webhook events from Stripe are signature-verified and processed exactly once.
3. If there is a security incident
- We contain the incident and stop any further unauthorised access.
- We assess which families and which data are affected, using the audit log.
- Where the law requires it, we notify the relevant regulator within 72 hours of becoming aware (for example the Dutch Autoriteit Persoonsgegevens).
- If the incident is likely to put you or your child at risk, we email affected parents without undue delay, explaining what happened, what we have done and what you should do.
- We record the incident, its cause and the fix, and change our systems so it cannot happen the same way again.
4. Reporting a vulnerability
If you believe you have found a security problem, please email support@mathidiajunior.com with the subject "Security". Please do not share the details publicly until we have had a reasonable chance to fix it. We acknowledge reports within one working day.
5. What you can do
- Choose a child code that is not a birthday or "1234".
- Remove devices you no longer use from your dashboard.
- Sign out of the parent zone on shared computers.
- Keep your account email secure โ it controls device approvals and deletion.
See also the child safety policy and the privacy notice.
Official references
These are the primary sources our policies follow. We review them at least every 12 months, and sooner when the guidance changes; any change to our policies is approved by the service owner before it takes effect.
- ICO โ Children's Code (UK) โ The UK Information Commissioner's 15 standards for children's privacy, default settings, profiling, parental controls and age-appropriate design.
- FTC โ COPPA compliance guidance (US) โ US Federal Trade Commission guidance on parental consent, privacy notices, children's data, security and deletion, including the 2025 Rule amendments.
- European Commission โ protection of minors under the DSA (EU) โ Commission guidelines (July 2025) on the safety, privacy and protection of minors online under the Digital Services Act.
- UAE โ child digital safety โ UAE government guidance on child digital safety and the relevant UAE legislation.
- W3C โ WCAG 2.2 (accessibility) โ The Web Content Accessibility Guidelines standard used as the audit baseline for the learning experience.