Skip to content

Family accounts

There are no child logins yet — on purpose.

A parent dashboard linked to a child’s account is planned, and five things have to exist before the first one is created. Here is the whole list, and where each one actually stands.

Meanwhile, everything for kids already works — with no account

Thirteen games, the kids’ Academy units, and the Story Shelf all run in the browser with nothing stored anywhere but that device. No sign-up, no email, no data leaving the machine. For a child, that isn’t a stopgap — it’s the better version, and it’s the reason we’re in no hurry here.

What we collect from your child

Nothing. No account, no requests to our servers while they play, no third-party anything, and nowhere for a child to type or upload. The page below lists exactly what stays in this browser — and gives you a button that clears all of it, without asking us.

The five things that come first

A child account is the highest-consequence thing this app could ever store. Building it before these exist wouldn’t be an incomplete feature — it would be an unlawful one.

Verifiable parental consent

Not built

COPPA requires consent from a parent BEFORE any data about a child under 13 is collected — and 'tick a box saying you're a grown-up' is not verification. This is the hardest of the five and it is first for a reason.

A published, plain-language data policy for minors

Not built

Exactly what is stored, for how long, who can see it, and how to end it — written so a parent can read it in two minutes without a lawyer.

Deletion that actually deletes

Not built

A parent must be able to erase a child's account and everything attached to it, in one action, and get confirmation it is gone. Not a support ticket. Not a 30-day queue.

Data minimization by construction

Partly done

The kids' arcade already stores nothing off-device. That discipline has to survive the arrival of accounts, which is when every product in history starts collecting more.

Moderation, reporting, and appeals

Not built

The same chain that keeps the feed closed. A child account without it is worse than no child account.

What the dashboard will show

  • Which units and games your child has finished, and which they haven't.
  • How many days they've practised — the same day-streak the adult track uses.
  • Badges earned, with the plain-English meaning of each one.
  • What the curriculum actually teaches, unit by unit, with its sources.
  • One button that ends the account and erases everything attached to it.

What it will never show

  • A transcript of anything your child typed. Not in games, not anywhere.
  • Which answers they got wrong, individually. Mastery is shown; failure is not itemized for an audience.
  • Location, device identifiers, or browsing outside Outpost.
  • Anything about other children — not names, not scores, not comparisons.
  • A leaderboard of any kind. Kids are never ranked against each other here.

Why the second list is as long as the first

A parent dashboard is surveillance infrastructure unless somebody decides in advance that it isn’t. Built without thinking, it becomes a monitoring tool aimed at a kid — every keystroke, every wrong answer, every session. That is a different product than this one, and a worse one. So parents get setup control and aggregate progress, and never a transcript. Your child gets to be bad at something in private, which is how anyone learns anything.

This page describes a plan, not a product. Nothing here is legal advice, and the COPPA summary above is our working understanding — the real policy will be reviewed by counsel before a single child account exists. If that review says the design is wrong, the design changes and this page will say so.