Privacy
Last updated October 30, 2026
NumZing is math practice for kids, run at numzing.com. This page says what NumZing keeps, who else sees any of it, and how to have it deleted. NumZing is a small independent project: it changes, and this page changes with it.
The short version
- Kids don't have accounts and don't give NumZing any personal information.
- A parent chooses a nickname for each kid; it doesn't have to be a real name.
- No ads, no trackers, and nothing is sold. NumZing counts visits to its public pages, and where they came from by kind, such as a search or a shared link. It never records who visited or who shared a link.
- Everything is stored on NumZing's own servers, not in a cloud database.
What NumZing keeps
- The family's account: the parent's name as they typed it, its email address, the password as a salted scrypt hash (the password itself isn't kept), its time zone, the school-year start month, the parent PIN as a salted hash made on the device, if the family uses one (NumZing never sees the PIN itself), and whether the person who runs NumZing has paused the account. Also its settings for notifications and email, such as the time for “Remind me about tonight's activity” and the day of the weekly report, and the biggest star milestone each kid's parent has been told about, so it's told once. And for Home's getting-started list, when a report and a lesson were first opened in the app, and when the list was put away.
- Weekly reports: each week's report for each kid (minutes, questions, stars, skills practiced and mastered, and the few sentences at the top), kept as it was sent so the app and the email show the same thing. Kids are named in it by an id, never their nickname.
- More people for the weekly email: if the parent adds them in Settings, up to two more email addresses (such as a co-parent's or a grandparent's), and whether each has confirmed. They have no account. They're never written to NumZing's logs, and each goes when that person stops the email, when the parent removes it, or with the account. The emails they get name the family by the parent's email address, so they know who asked.
- How a new account found NumZing: a link a parent shares (an invitation, a week's picture, a certificate) carries only the kind of link, such as “week”. If someone signs up within 30 days of opening one, the account keeps that kind, and NumZing counts sign-ups by kind for each day. Nothing in the link says which family shared it, so NumZing can't tell, and never records, who shared or who came from whom. The kind waits on the device that opened the link until then, and nothing else about the visit is kept. NumZing also counts sign-ups each day by the kind of place the device last came from (the kinds below), and doesn't keep that on the account.
- Visits to the public pages: when someone opens the home page, the level check, the sample test, the Beyond school puzzles, the lessons or a lesson in a browser without being signed in, NumZing adds one to that day's count for the page. For the home page it also adds one to a count of where the visit came from: a search, a social site, another site, a shared link, a campaign link NumZing posted itself (tagged with where it was posted), or straight here. Finishing any of the three, or starting a lesson's questions to try, is counted the same way. The sample test and the Beyond school puzzles send only the grade band, and a lesson only which lesson it is, to get their questions; the answers stay on the page and go when it closes. Only the kind is sent, never the address of the page the visitor came from, and nothing that could tell one visitor from another. So that a device counts once a day, it keeps the date it last counted each page. Nothing is counted in the NumZing app, or once a family is signed in.
- Security reports from the browser: on the website, if a page tries to run a script NumZing didn't put there, the browser tells NumZing which page and what kind of script. NumZing counts these by kind and keeps nothing else.
- Each kid's profile: the nickname, grade and avatar the parent chose, and settings such as read-aloud, the daily goal and how long a usual session is, whether the facts warm-up and Beyond school are on, and whether the kid is preparing for a math contest, with the contest's day if the parent gives it. If the parent says what school is on, the skills they picked and, when it came from a school report, which kind of report and the parts they ticked as low (never a score). If the 8-question level check was taken on the same device in the 30 days before the kid was added, and the parent leaves “Start from the level check” on, each of its questions' skill, level and whether it was right first try, to set where practice starts. Until then the check's answers stay on that device.
- Practice: each answer (with the basic fact it asked, such as 7 × 8, for the facts grid), how long it took, how far into the session it came (breaks left out, so practice time and break time can be told apart), whether a hint was used, the drawings on the scratch pad, and the kind of device a session was played on (such as “iPad”), so a report waiting for its answers can say which device to open.
- Practice tests: for each contest-style practice test a kid sits, the questions it had, the answer picked for each (or none), how long each took, which ones the kid marked to come back to, the time used, and the score. Its time counts toward the kid's practice minutes and its points toward their stars, as practice does. Scratch pad drawings in a practice test stay on the device and are never sent.
- What parents add: rewards they set, questions they flag (in a report or a practice test), with any note they write, and which of a report's suggestions they marked as trying or tried.
- Notifications: for each device a parent turns them on for, the address the browser gives for delivering them (in the NumZing app, the device's notification token instead), and a name for the device such as “iPad”.
- Fault reports: when the app breaks on one of the family's devices, what failed: the error message, which screen and which kind of request, and the app's version. Never a page address, and never anything anyone typed, drew or answered. Parents can switch these off in Settings, and then nothing is stored.
- Bug reports: when a parent sends one from Settings, what they wrote, up to two screenshots they chose to add (made smaller as they arrive), the app's version, the kind of device, the screen they were on, and the last few faults the app noticed. A screenshot shows whatever was on the screen, which can include a kid's nickname and answers. Only the person who runs NumZing reads them.
- Request logs: NumZing's servers note each request (which part of NumZing was asked, when, and the account's number, never its email address) to find and fix problems.
Kid mode has no microphone, camera, photos, location, contacts or typing of words. The app also keeps some things on the device itself: the running session or practice test, answers waiting to sync, questions for starting offline, and copies of what the parent screens last showed (the kid list, stars and goals, progress, the week, and reports), so they open at once and work offline, the rewards the last few sessions reached, for the grown-up to see on the report, which mastered skills and star milestones Home has already celebrated, and how the app looks on that device (light or dark, and its colours), which is never sent. Signing out removes the copies, the offline questions, the rewards and what Home celebrated; a running session and answers waiting to sync stay, kept for the account that made them: another account signing in on the same device doesn't see or send them, and they're sent when their own account signs in again. An answer NumZing won't accept is removed from the device. “Sign out of every device” in Settings ends the sign-in on all of them at once. A new email address or password signs out every other device, and NumZing emails the old address to say it changed.
Who else sees any of it
- Cloudflare carries all traffic to numzing.com and handles its encryption, so data passes through Cloudflare on the way. Cloudflare also forwards email sent to support@ and privacy@numzing.com. On the website, signing up, asking for a password reset, and signing in after a few wrong passwords show Cloudflare's Turnstile check, which looks at the browser (and its address) to tell a person from a program; it sets no advertising cookies.
- The tutor's note. After a session, a language model writes a short note for the parent from facts NumZing chooses: skill names, counts, and a few questions with the answers given. The same kind of model writes the few sentences at the top of each kid's weekly report, from that week's counts and skill names, only ever on NumZing's own computer. The kid's nickname is never sent; NumZing adds it afterwards. The model normally runs on NumZing's own computer. When that computer is busy or unavailable, a note's facts may go to OpenRouter, a hosted service, which NumZing asks to use only providers that don't store or train on what they receive.
- Resend sends NumZing's emails, such as the link that checks an email address, and the weekly report by email for a family that turns it on in Settings (each kid's nickname, the summary at the top, minutes, questions right on the first try, stars, skills mastered, practice-test scores and anything worth a look that week), so it receives the address and the message.
- Pushover delivers a notification to the person who runs NumZing when an account is made, with the email address it was made with. Nothing else about the account goes with it.
- The people a parent adds to the weekly email get that same weekly email, once they've confirmed from the one email NumZing sends them first, which gives the parent's name as they typed it. Each weekly they get has a link that stops it for them, with no sign-in.
- Anyone a parent shares a picture with. The week's picture and the certificates (a star milestone, a skill mastered with its standard) are drawn on the parent's device and go only where the parent sends them. They carry no name, age, school or score, unless the parent ticks the box to show the kid's nickname on that one picture; the box starts unticked every time.
- Push services. In a browser, a notification reaches a device through the browser's push service (Google, Apple, Mozilla or Microsoft), and its content is encrypted so that the push service can't read it. In the NumZing app for iPad, iPhone and Android, notifications go through Google's Firebase Cloud Messaging, and on to Apple on an iPad or iPhone. There the notification's words travel readable to Google and Apple: for a report, the kid's nickname and how many questions they answered and got right first time, and how many skills they newly mastered; for a practice reminder a parent set, the kid's nickname; for a star milestone, the nickname and the number of stars; for tonight's activity, if the parent turns it on, each kid's nickname and the activity's name. Nothing else about the kid goes with it.
- YouTube, only if someone presses play on a lesson's video. A lesson may have a video from NumZing's own channel. Until someone presses “Watch the video”, nothing is loaded from YouTube. Pressing it on the website loads YouTube's privacy-enhanced player (youtube-nocookie.com), so Google sees that browser's address and what it watches, under Google's own policy; in the app it opens the video on YouTube. NumZing sends YouTube nothing about the family or the kid. Videos are never shown in kid mode.
Nothing else leaves NumZing's servers, and nothing is shared for advertising or sold.
How long it's kept
- Answers, and what NumZing works out from them, are kept while the kid's profile exists.
- Scratch-pad drawings are deleted after 12 months, and sooner once a kid's drawings pass 50 MB: the oldest go first.
- Records of notifications sent, fault reports and request logs are deleted after 30 days.
- Bug reports are deleted after 90 days.
- Weekly reports are deleted after 400 days.
- Every night NumZing makes an encrypted copy of its database, kept on NumZing's own computers for up to 30 days in case one fails. Anything deleted in the app is gone from these copies within 30 days.
- NumZing keeps daily totals about itself, such as how many answers were given that day, how many visits each public page had, and how many sign-ups came from each kind of shared link, for ten years. They say nothing about any one family or kid.
- Deleting a kid in the app deletes everything about that kid straight away: profile, answers, drawings, reports, practice tests, rewards and flags.
- Deleting the account in the app deletes it, every kid on it and everything about them straight away, along with its email address, password hash, notification devices and bug reports.
- An account whose email address is never verified is deleted after 7 days.
Children
NumZing is used by children, under a parent's account. Sessions start from that account, and a family that chooses a parent PIN uses it to guard leaving kid mode. NumZing doesn't collect personal information from children: a kid produces answers, timings and drawings, and nothing else.
Your choices
- Delete a kid, and everything about them, from the kid's Edit page.
- Turn notifications off for a device in Settings.
- Remove anyone you added to the weekly email in Settings. They can also stop it themselves, from the link in any weekly email they got.
- Turn fault reports off in Settings.
- Delete the whole account in Settings, under Delete this account (how, and what goes: Deleting your account).
- To get a copy of your data, email privacy@numzing.com. It's done within 30 days.
Changes
When this page changes, the date at the top changes. A change that shares data more widely is announced in the app before it happens.
Questions: support@numzing.com · Privacy: privacy@numzing.com