Getting started

Four steps from signup to your kid's first game. You create the account, you verify that you're the parent, and your kid never needs an email address.

1. Create your parent account

1. 1

   Sign up as the parent

   Go to parent signup and create your account with your email. Kids never sign up themselves; FuzzyCode accounts always start with a parent.

   

2. 2

   Confirm your email

   You'll confirm the address with the 6-digit code from your inbox. That address is the family account's anchor: it keeps the account reachable for the things only you should control: approvals, billing, and privacy.

3. 3

   Verify that you're the parent

   Children's privacy law (COPPA) requires us to check that a real parent or guardian is consenting before a child can use FuzzyCode. Verification happens with a payment card, which doubles as your subscription setup. The children's privacy notice explains exactly what we collect and why.

2. Add your first kid

1. 1

   Create their profile

   From your Parent Hub, add a kid. You choose what you call them (a family label only parents see) and, separately, a public username that only ever appears on sharing surfaces you've approved. Neither has to be their real name.

   

2. 2

   Give their okay-to-use consent

   Each kid has their own consent for using FuzzyCode privately. This is separate from sharing: saying "my kid may build things here" never means "my kid's projects may go public." Publishing always needs its own approval, every time. More in Approvals.

   

3. 3

   Optionally, set up their own login

   You can give your kid a private login name and password so they can sign in by themselves at fuzzycode.dev/kids/login. No email needed, and parent accounts are rejected on the kid sign-in page. You can change the password, sign them out everywhere, or disable the login any time.

   

What your kid sees

The kid sign-in page asks for "Your private login name" and their password, nothing else. Once they're in, they land in their own workspace: their projects, their assets, nobody else's.

3. Let them build (or build together)

Two ways to run it:

• Their own login. Your kid signs in at /kids/login and works independently. You see everything from your side.
• Working as your kid. From your parent account you can switch into a kid's workspace yourself, great for building together or helping when they're stuck.

Point them at the kid guide to making a first game. It's written for them.