Terms — Piplab

The service

Piplab helps children aged roughly 10–13 turn an idea into a working build — a plan, then blocks and code — with an AI assistant called Pip alongside them. It is a building tool with a deliberately narrow assistant, not a general chatbot: Pip helps make things, and declines everything else. That refusal, and the other limits described on the safety page, are part of the service itself. They are not optional features, and asking us to switch them off is not a request we can grant.

Two things Piplab is not. It is not a social platform — there is no feed, no comments, and no messaging between users. And it is not infallible: Pip is an AI, and AI is sometimes confidently wrong. That matters most in challenge marking, which is automated. The marking is built to quote the child's real work, to say "not yet" rather than "wrong", and to let them hand in again as many times as they like — but a cross on a criterion is a machine's reading of a build at one moment, never a verdict on a child. Tutors and parents should read it that way, and we design it to be read that way.

Accounts

Adults open their own accounts with an email address and agree to these terms for themselves. Children cannot open accounts: every child login is created by an adult — a parent or a tutor — and that adult accepts these terms on the child's behalf and answers for the login they made. Keep your password to yourself, use one login per person (progress and marking make no sense otherwise), and tell us if you think an account has been accessed by someone else.

There is no automated password recovery by email yet. A child's password is reset by the grown-up who made their login; a grown-up who loses their own password should contact us.

If you are a parent

The logins you create for your own children are yours to look after: you choose the username and password, you reset the password, and you are the one who decides — with us — whether anything they make ever goes public. You are responsible for your child's use of Piplab in the same way you are responsible for it anywhere else online, and we have built the product so that this responsibility is actually exercisable: their work is visible to you, and nothing about their account happens over their head or behind yours.

If you are a tutor or run a club

You are responsible for the student logins you create: keeping the roster accurate, holding the passwords safely, and using your access to students' work only for teaching. Most importantly, you must have each parent's permission before you create a login for their child. Piplab cannot obtain that consent for you — we do not know who your students' parents are, by design — so creating a student login is your statement to us that the permission exists. Put Piplab's privacy page in front of parents when you ask, and keep a record of their answer. If a login turns out to have been made without permission, tell us and we will delete that student's data promptly.

Acceptable use

Use Piplab to learn and to build things. That is what it is for, and all it is for.
Do not try to work around the guardrails, overload the service, or make Pip do things the safety page says it will not do. The limits are load-bearing.
Do not attempt to reach other people's data — other students' builds, other accounts, other families. The product is built so that this fails; trying is still a breach of these terms.
Do not put other people's personal information, or anything unlawful or hateful, into builds — especially published ones.

If an account is used to break these rules, we can suspend it. For a child login we will talk to the grown-up who made it first wherever possible — the aim is always to fix the situation, not to punish a ten-year-old for curiosity.

Children's work & ownership

A build belongs to the child who made it. Piplab does not own children's work, and does not use it for anything beyond running the service: storing it, showing it to the child and their grown-up, sending it to the AI so Pip can help with it and mark it (see where the AI fits), and — only where publishing is switched on — showing the published version at its public address. You give us permission to do exactly those things and nothing more. Delete a build and that permission ends with it.

Publishing is a choice, and for children it is a grown-up-gated one: child logins start with publishing switched off. A public page can always be taken down — delete the build, or ask us to switch publishing off for the account — and because the check runs every time the page is opened, taking it down takes effect immediately.

Pricing & billing

Nothing on Piplab charges money today. Billing is not connected: no card is ever charged, and no card details are stored or sent anywhere — the checkout page says exactly this on its face. The prices on the pricing page are what the paid plans will open at when billing arrives. When it does: paid plans will bill in advance and be cancellable at any time, cancelling will never delete anyone's work, and prices can change only with clear notice on the site before your next renewal — never mid-cycle.

What we promise — and what we can't

Piplab is young software, and we would rather say so here than have you discover it. It is provided as-is: we work to keep it up, safe, and correct, but we cannot promise it will always be available, that the AI will always be right, or that a build will never be lost — keep the "download" button in mind for work that matters. To the extent the law allows, we are not liable for indirect losses from using Piplab, and our total liability to you is capped at what you paid us in the past twelve months — which, today, is nothing. None of this limits anything the law says cannot be limited, and none of it is a licence for us to be careless with children's data: the promises on the privacy page stand on their own.

Leaving, and what happens to work

Stopping a paid plan (when they exist) moves the account to the free plan. Nothing is deleted — builds, child logins, and everything they have made stay exactly where they are.
Deleting an account is done by asking us via the contact form, and removes the account and its work within 30 days, as the privacy page describes.
If we ever suspend an account for breaking these terms, the work in it is not held hostage: the account's owner — for a child, their grown-up — can still ask for a copy of the builds, or for deletion.
If Piplab ever shut down, we would say so on the site with enough notice for everyone to download their work.

Governing law

Piplab is made and operated in Anguilla, and these terms are governed by the law of Anguilla. If some part of these terms turns out to be unenforceable, the rest still stands.

Changes & contact

When these terms change, the date at the top changes, and a change that actually affects you gets flagged plainly on the site — we do not send email, so this page is where changes live. Continuing to use Piplab after a change means the new terms apply; if you do not agree with a change, stop using the service and, if you want, ask us to delete your account.

Questions about any of this: the contact page reaches us, and hello@piplab.ai is the same inbox.

These terms are written in plain words on purpose — terms a parent cannot read protect nobody. If anything here is unclear, ask us.

Terms of service