How it works
A child creates. A parent approves. A school stays in touch. Here's the whole flow, screen by screen, from the real app.
Kids never sign themselves up. Every child's account is created by a parent or guardian.
Three views
One account per person, and each one shows only what that person should see.
A feed of buddies you approved, a profile you set up, and a red SOS button that reaches the adults you chose.
See how
One dashboard for every child: what's waiting for your yes, what they've been doing, and how close they are to their screen-time limit.
See how
Attendance the parents actually see, homework and announcements sent to one class, and messages tagged to a child.
See howLoop one
Your child writes a post and taps share. Nothing happens yet. The post is held, and a request lands with you.
You see it as a count on your dashboard, before anything else on the screen: four requests are waiting for you. Open one and you can read exactly what your child wrote. Approve it and it goes live to their buddies. Do nothing and it stays private.
Posts, stories, comments and buddy requests all take this route. So do profile edits: if your child changes their name, username or photo, the change is held and the old version stays until you approve it.
Settings also hold a daily or weekly round-up, at a time you pick, telling you how many unread notifications are waiting. The requests wait on your dashboard until you get to them, however you set it.
The child's side. Their feed, and the posts that went live once a parent said yes.
The parent's side. The same moment, on your phone: “Sita has requested permission to publish a new post.”
Loop two
Children cannot add each other on their own. One connection takes four separate approvals, in this order:
Two children, two families, four yesses. If any one of them declines, the connection simply never exists, and neither child can message or comment across it.
Loop three
A second view opens up inside the same app. Nothing else changes: the approvals, the buddies and the screen-time limits work exactly as before.
The teacher marks the class present, absent, late or excused and hits submit. You see the result on your child's card the same morning, and you get a notification when they arrive at school, down to the minute.
Homework, announcements and circulars are posted to one class rather than shouted at the whole school, and they land in your feed and your child's at the same time.
When you need to talk to a teacher, you can message the teachers who actually teach your child, and every message is tagged to that child so it never lands without context. The app refuses any other pairing.
One honest exception. School and class posts are moderated by the school, not held for your approval. Enrolling your child is the consent.
Getting started
Adults open the family account. A child account created any other way is refused outright, by the server, not just hidden in the app.
You add each child and set their age range: 3 to 7, 8 to 12 or 13 to 17. It shapes what they see and what they can do, and only you can change it.
Schools don't sign themselves up. We set the school up alongside you: classes, subjects and the timetable, then the roster in one CSV.
Talk to us about a pilotThe controls behind it
Every one of these is in the app today. Nothing here is coming soon.
Almost. Posts, stories, comments, buddy requests and profile edits all wait for a parent. There is one honest exception: if your child's school is on YoungCreator, anything tagged to their class is moderated by the school, not held for your approval. That covers the school's own posts, like homework and announcements, and what your child submits back, like a homework submission. Enrolling your child is the consent there.
Not through the app. Two children are only connected after four separate approvals, and until that connection exists there is no way to send anything across it. The adults around the account are ones you can name. You add some of them yourself: a second guardian, or a trusted contact such as a grandparent. If your child's school is on YoungCreator, the list also takes in any other active member of that school, because the school side of the app is open to the school's whole active membership: staff, but also other parents and students, rather than their class teacher alone. Our own team can reach accounts too, for moderation and support.
Read their feed, see what their approved buddies have shared, react to it, and use the school view if their school is on YoungCreator. On the social side, anything other people would see waits for you first: a post, a story, a comment, a new buddy, a change to their profile.
One approval from each side. The request goes to the sending child's parent first, then the other child accepts, then that child's parent approves. Four yesses in total, spread across two families, and the two children are only connected at the end of it.
No. Approvals, buddies and screen-time limits work whether or not the school is involved. If the school does join, an extra school view appears in the same app with attendance, timetable, homework and messaging. Schools are set up with our team rather than signing themselves up, so if yours is interested, put them in touch with us.
Create a parent account, add your child, and set the rules before they post a single thing.