Safety

The limits are in how it is built, not in a settings page.

There is nothing here for you to configure, and nothing to remember to switch on. Pip only helps build things. The code it writes has to be able to stop. And there is no one for a child to talk to except the thing helping them make something.

A parent reviewing their child's work at home
Scope

There is no blank chat box

Pip only helps build things with code. Homework answers, essays, personal questions, who won the game — every one of them comes back as an offer to make something instead. It is a rule the model is given on every single request, not a filter watching for bad words.

Runaway code

Nothing it writes can fail to stop

Every program has to have an ending someone can point at: no endless loop, no timer that restarts itself, no code that writes and runs more code. A program that will not stop reads to a child as "I broke the computer", and it is the one failure a beginner cannot escape.

Isolation

Their program cannot phone out

Before a child's first line of Python runs, the sandbox has fetch, XMLHttpRequest, WebSocket and eight other ways of reaching the network deleted from it. Not blocked by a setting that could be turned off — removed, so there is nothing to turn back on.

No one to talk to

No feed, no messages, no strangers

There is no child-to-child anything in Piplab. No profiles to browse, no comments, no direct messages, no way for an adult to contact a child through it. The only inbox that exists carries messages between a child's own builds.

Removed before their code runs
fetch XMLHttpRequest WebSocket EventSource Worker SharedWorker importScripts Request Response RTCPeerConnection BroadcastChannel sendBeacon
Deleted from the Python sandbox at start-up, every run, before any of your child's code is loaded.

The safest setting is the one nobody can forget.

A control panel only protects a child whose parent found it, understood it and got it right — and it stops protecting them the moment somebody toggles the wrong thing. So Piplab does not have one.

Instead the boundaries are missing capabilities. Their program cannot reach the internet because the ways of reaching it are not there. Nobody can message your child because there is no messaging. You cannot get these wrong, because there is nothing to set.

Common questions

Can they ask it about anything?

No. Ask for an essay, a homework answer or last night's score and it says the same thing every time: that is not something I can help build — want to make a game, a quiz, or a tool that solves a real problem instead?

Can another child contact mine?

No, and not because we moderate it well — because it does not exist. There is no messaging, no comments and no profiles to find. A child cannot be reached through Piplab by anybody.

Can their program reach the internet?

A gadget program cannot: the sandbox has every network function removed before it starts. Pip also refuses to write network calls, polling or retry loops into anything, including websites and games.

Can it use the camera or microphone?

Only if your child presses a button to start it themselves — never when a page loads. What the camera sees is drawn on their own screen and is not uploaded anywhere.

Can I see what they have been doing?

Yes. Every build is saved with its full history, so you can open any version and see how it got there. An individual account is set up and held by a parent, so what they see, you see — there is nothing hidden from you and nothing hidden from them.

Is their work used to train AI models?

Piplab does not train any model on your child's work. Their request is sent to the AI provider that writes the reply, and that provider's data policy applies to it — we name the provider and link its terms in our privacy notice.