For parents

How FuzzyCode keeps kids safe

A straight answer, because you're trusting us with your kid. Three layers do the work: what kids simply can't do, what gets checked automatically, and what only you can approve.

What kids simply can't do

What gets checked automatically

An honest boundary

Automatic checks are filters, not judgment. The judgment call on anything your kid wants to show the world is reserved for you: that's why publishing is parent-approved per version rather than machine-approved. We'd rather give you real control than promise magic.

The controls you hold

ControlWhat it does
Disable a kid's loginStops them signing in, immediately, until you re-enable it. You can also sign them out everywhere.
Change their passwordResets the private login credentials you gave them.
Sign them out everywhereEnds their active sessions on all devices right away.
Approve or reject sharingPer project, per version. Published projects can be unpublished later through privacy controls.
End a friendshipEither family can disconnect a friendship at any time.
The child login controls in the kid detail page
The login controls, in each kid's hub.

If something looks wrong

Tell us through the parent contact form. A human reads it. For privacy-specific concerns and your legal rights, see Privacy & your rights.