Privacy at Mr. Aube and Friends
Last updated September 26, 2026 · Written in plain language on purpose · Read the full Privacy Impact Assessment
The short version
- Everything about your child stays on your device. Learner names, class rosters, and game play history live in your browser's local storage. They are never sent to us. We couldn't look at them if we wanted to — they don't exist on our servers.
- We collect the minimum to run your account: your (the adult's) name and email from Google or Microsoft sign-in, and subscription status from Stripe if you subscribe.
- No ads. No analytics trackers. No data sales. Ever. There is no advertising, no third-party analytics, and no tracking of children anywhere on this site. The site loads nothing from anyone else, with one exception we spell out below: the teaching videos embedded on the four strategy pages for grown-ups.
- Games never ask kids for anything — no names, no photos, no chat, and no “upgrade now” buttons inside child-facing content.
Your child's information: it stays with you
Our public address is now mraube.ca, served by the same Microsoft Azure application. This domain change adds no tracker or new data collection. The previous Azure address remains available. Because browser storage is separate for each address, saved learner data does not move automatically: export your device backup at the old address and import it at mraube.ca if you want to bring that data with you. The backup stays under your control.
The Learners, Progress, Rosters, and Trophy features all run on a simple rule: children's data never leaves the device it was created on. When you add a learner, you enter a first name, an optional last initial, and (if you like) their grade — so progress is framed against the right year's expectations — and nothing else. No birthdays, no photos, no emails. That profile, and the record of which games were played and how the answers went, is stored in your own browser's storage (IndexedDB), on your own computer or tablet.
Because of this, progress doesn't follow you between devices — play at school won't appear at home, and clearing your browser data removes it. That's a real trade-off, and we chose it deliberately: it is the strongest privacy protection we can offer a seven-year-old. You can export any learner's history as a file, or delete it completely, from the Learners page at any time.
If we ever offer optional cloud sync so families can back up progress, it will be off by default, require a parent or guardian's express opt-in consent, and come with its own clear explanation — and this policy will be updated first.
Classroom boards
Boards are the one part of the teacher toolkit that is saved to your account rather than only to your device, so a board you build at school opens on the same account at home. What syncs is the board layout and each widget's settings: which widgets you placed, where they sit, and the options you chose — including any text you type into a Text, Spinner, or QR-code widget. That is stored with your account in Microsoft Azure's Canada East region and is deleted when you delete the board.
Class rosters stay on the device. Student names, status-board assignments, and whiteboard drawings are never sent to us — a board records only which roster a widget points to, never the names inside it. Because widget text does sync, please don't type student names into a Text, Spinner, or QR-code widget. Use a roster-backed widget instead — the name picker, group maker, and status row read names straight from your device.
Shared computers
A staff-room computer, a classroom sign-in, or the family tablet usually carries more than one adult. Two things follow from that, and they work differently on purpose.
A board's offline copy is kept per account. Your board is cached in the browser so it keeps working when the network does not, and that cache is stored under a key that carries your account id: mr-aube-board:<userId>:<boardId>. It used to be keyed by the board alone, so on a shared computer the second teacher to open a board saw the first teacher's cached copy of it — including anything typed into a Text widget. A cache left from before that change is moved into the account that opens it, once, and the old key is deleted in the same step so no one else can pick it up.
Learner profiles are not per account — they cannot be. They live in the browser rather than in your account, which is exactly why we never receive them; the cost is that anyone who signs in on that computer sees them, and signing out leaves them behind. The Learners page says so in plain words and carries a Clear this device's learner data control that erases every local store — profiles, play history, term baselines, trophies, class rosters, status assignments and whiteboard drawings — in one action. Export a backup first if you want to keep any of it.
What we do collect (from adults)
Account: when you sign in with Google or Microsoft, we store your name, email address, an account identifier from the sign-in provider, and the profile picture that provider supplies. We use this to know which account is yours and what it can access.
Billing: payments are handled by Stripe. Your card number goes to Stripe, not to us — we never see or store it. We keep Stripe's reference IDs and your subscription status so the site knows your membership is active. Promotional access codes you redeem are recorded against your account.
Feedback and teacher-code requests: when you send feedback from inside the site, or ask for a classroom code on the For Teachers page, your message is filed as a private issue in our development tracker, which is hosted by GitHub in the United States. A feedback note carries your email address, the page you were on, and your browser and screen size so we can reproduce the problem. A teacher-code request carries the name, school, school email, and class size you typed. We never ask for anything about a child and nothing about a child is attached automatically — please don't type a child's name or details into the message, because whatever you write is forwarded word for word. Neither kind of message is stored in our own database.
Operational logs: like nearly every website, our hosting platform (Microsoft Azure) keeps short-lived technical logs used for keeping the service running and secure. These logs are kept for 30 days. Our structured server-failure reports use fixed operation codes and error categories, without copying request contents or local learner records. We do not collect browser error reports or session recordings.
Account data is stored in Microsoft Azure's Canada East region, on Canadian soil.
What we don't do
- No advertising, anywhere.
- No analytics or tracking SDKs — not on the site, and especially not in the games.
- No selling, renting, or sharing personal information.
- No using anyone's data to train AI models.
- No behavioural profiling of children, and no manipulative design: no loss-based streaks, no children's scores designed to shame, no upsells or locked-content teasers shown to kids.
- No collection from children at all — the site is operated for and billed to adults.
The one exception, spelled out: the four strategy pages written for grown-ups embed Mr. Aube's own teaching videos from YouTube. Opening one of those four adult pages therefore contacts YouTube (a Google service), which can see that a browser loaded the video player. We use YouTube's privacy-enhanced no-cookie mode for the player so it sets no tracking cookie unless someone presses play. Nothing else on the site loads anything from anyone else — the strategies index that lists the videos shows pictures we host ourselves, and no game, tool, worksheet, or member page makes a third-party request of any kind, with no child-facing surface containing an embed.
Cookies
We use only the cookies needed to keep you signed in (session and sign-in security cookies). There are no advertising or analytics cookies.
Consent and children
Under Canada's federal privacy law (PIPEDA), consent for a child under 13 must come from a parent or guardian. Our answer is structural: we designed the product so that your child's information is never collected by us in the first place. You — the parent, guardian, or teacher — stay in control of the only copy.
Teachers: because no student personal information is ever disclosed to us, using the local-only learner and roster features does not send student data to a vendor. Our Privacy Impact Assessment is written to support your district's review process.
Your choices
- See, export, or delete a learner any time on the Learners page — deletion is immediate and real, because the only copy is yours.
- Cancel a subscription from your account settings; billing stops through Stripe.
- Export everything we hold about you from Settings → Your data — the account record, your subscription status and any redeemed codes, as a file. (Your children's profiles are not in it: they were never ours to send.)
- Delete your account yourself from the same place, Settings → Your data. It removes your account record, your subscription and access-code details, and your saved classroom boards. A live subscription has to be cancelled as part of the same request — we will not quietly end a plan you are still paying for, and we will not delete an account that is still being billed. You can always contact us (below) instead and we'll do it for you.
Contact
Mr. Aube and Friends is run by a New Brunswick teacher. Questions or requests about privacy, including access to or deletion of your account: email privacy@zaiphr.ai. You can also reach us through the Mr. Aube and Friends Facebook page or the YouTube channel, and we'll respond as quickly as we can.
Changes
If this policy changes, we'll update this page and the date at the top. We will never weaken the children's-data promise above without asking for your express consent first.