Privacy Policy — JaxillMind
JaxillMind collects nothing at all. There is no account, no sign-in and no email to give. No analytics, no advertising, no third parties, and nothing about you or your child ever leaves the device.
What we collect
Nothing. Not one thing. The app has no account, no sign-in screen and no email field, and it transmits no data of any kind. No analytics, no advertising identifiers, no third-party services. All twelve games are open from the first tap and nothing is asked of you in return.
What stays on your device
The player names you type and the record of play — which games were played, for how long, how many items were answered, how many were correct, and the difficulty level reached. This is stored in your device's local storage and is never transmitted anywhere. We cannot see it. Nobody can see it but you.
Children's privacy
JaxillMind is built for children and is designed so that there is no children's data to protect: nothing about your child is ever collected and nothing ever leaves the device. Player names are typed by you on your own device and stay there. We receive nothing from anyone — not from a child and not from a parent — so there is nothing to sell, nothing to share with advertisers or data brokers, and nothing that could be used to track anyone. Because no personal information is collected, no parental-consent flow is needed and a child is never shown a sign-in screen.
Deleting your data
You can delete an individual player or erase everything from Settings inside the app. Deleting the app also removes all of it. Because we never receive any of it, there is no copy anywhere else and no request you need to send us.
The report you share
The weekly progress report is built on your device. If you choose to share it — with a teacher, a paediatrician, or anyone else — you send it yourself using your own device's share options. The app has no recipient and no ability to send anything.
How you can check this
Every claim on this page is enforced at build time against the shipped app, not merely asserted. The build is checked before release to contain ZERO network calls of any kind, and it is refused if it contains even one. The parental gate is checked by driving the real app: an automated test solves the gate, opens the link, then taps the same link again and refuses the build unless the gate asks a second time. If either check fails, the app does not ship.
Changes
If this policy ever changes, the change will be dated here and the previous version will remain available. A change will never apply retroactively to data we never had.