Is it safe for my kid to share what they make online?

Mostly, no — not on the open internet, and it's worth being straightforward about why. Social media, YouTube comments, public forums, and most "share your creation" corners of the internet were built for adults posting to strangers, not for a seven- or eleven-year-old showing off something they made. A kid's excitement about finished work is real and worth protecting. It's the venue that's usually the problem, not the impulse to share.

That's the honest split here: what makes open-internet sharing risky for a kid, the guardrails that actually address those risks, and what sharing built for a child looks like instead — the reason Kubrio's sharing model exists the way it does.

Why the open internet isn't built for a kid to post to

Three things make general sharing platforms a bad fit for a child, and none of them require imagining a worst case — they're just how those platforms work by design.

• Strangers can reach in. Public posts on social media, YouTube, and open forums can be commented on or messaged by anyone with an account, including people with no business talking to a child. The default on most platforms is an open door, not a closed one.
• Personal information spreads further than intended. A face, a full name, a school logo in the background, a location tag — any one of these can turn a proud share into a way for a stranger to identify or find a real child.
• Permanence is real, and undoing it is hard. Once something is public online, it can be screenshotted, reposted, or cached somewhere a takedown request never reaches. "I'll delete it later" is a weaker guarantee than it feels like in the moment.

None of this means a kid's project is dangerous to make. It means places built for adult posting, where the audience is the whole internet and moderation is reactive, are the wrong venue for a child's work — almost regardless of how careful the child is.

The guardrails that actually matter

If your kid wants to share something they made — a drawing, a video, a story — a few concrete guardrails do most of the real safety work, whatever platform is involved:

1. No identifying details in the post itself — no last name, no face if avoidable, no school, no location, nothing that lets a stranger find the real child behind the work.
2. A parent controls who the audience is, not the kid alone and not "whoever's online right now."
3. No open comments from strangers. Reactions from people the family actually knows are a different thing entirely from an open comment section.
4. Takedown is instant, not a support ticket that might get answered eventually.
5. The kid understands it's public before it goes up — not a surprise they discover later.

Run any sharing decision — a school project uploaded somewhere, a video on a family YouTube channel, a drawing on a public art site — through those five, and you'll know quickly whether it's the safe kind of sharing or the risky kind wearing a friendly interface.

Put them together and you get a shape: private by default, a ladder toward wider audiences, and a parent holding the key at the one step that matters — going public. A kid should get the real pride of showing finished work without a family gambling on their child's safety to get there. That's a design problem, not an impossible one, and it's the one Kubrio was built around.

How Kubrio built sharing this way

Every project a Kubrio kid makes starts private — visible only to the kid and the parent, full stop. From there, sharing moves up a short ladder, and a kid can't skip to the top alone.

The next level is visible only to the small group of kids in the same sprint — the audience behind Demo Week, where kids show finished work to the peers they've been building alongside all season. It's still inside Kubrio's walled garden: no strangers, no open messaging, no public comments. Kids can react to each other's work in a Gallery built for exactly that, with nothing reaching outside the group.

Going further — a public page anyone with the link can open, at kubrio.com/made — requires a parent's consent, every time. Your kid cannot make anything public alone. When something does go public, Kubrio is deliberate about what shows: first name only, no last name, no face required, no contact information, and no comments from strangers. Generated share art is built non-identifying from the start, not cropped after the fact.

If anything moves up a level, it shows up in the plain weekly summary Claire sends you, so you're never finding out from somewhere else. The AI Crew that worked alongside your kid has no say in whether the project ever leaves the family — that decision is yours, every time. And if you change your mind, takedown is instant: hide or remove anything from the parent dashboard, no reason required, and it disappears from public view right away. Full detail lives on safety and data and safety.

Where this shows up for a real kid

In Sketchling, a kid draws the key frames of their own story on real paper, and the finished film lands in the portfolio and, at Demo Week, in front of their sprint group. In Origin Stories, a kid publishes a comic issue under a pen name they picked, building toward that same cohort audience long before anyone decides whether to take it further. In Book Club, a kid records a short podcast-style interview about a book they actually read, and it stays private, goes to family, or gets shared, on the family's own timeline. In every case, the finished thing is real, the first audience is safe by construction, and going wider is a parent's call, not a default.

A checklist you can run before your kid shares anything, anywhere

You don't need Kubrio to run this test. Before your kid posts a project anywhere, check for:

1. Does the post include a name, face, school, or location that could identify your child to a stranger?
2. Who decides the audience — you, or whoever happens to be online?
3. Can strangers comment or message in response to the post?
4. How fast can it come down if you change your mind?

A platform built for kids should pass all four without you having to fight its settings to get there. A general social platform will fail at least the first two by default — which just tells you what job it was built for, and what it wasn't.