Schools
Safeguarding is not a policy document here. It is the plumbing.
A named officer, a route to report something, and access that is recorded every single time it is used — on a platform where the log of what was done cannot be altered by anybody, including us.
Who looked, and why
Safeguarding tools fail in one of two ways: nobody can reach what they need, or anybody can reach anything. The answer to both is that access exists and is always recorded — an unlogged look is the thing that turns a safeguarding tool into a surveillance one.
The log of what was done cannot be edited or deleted. The database refuses it, and the screens that read it are incapable of writing, so looking at the evidence cannot alter the evidence.
A record of who was there, that stands up
Every meeting produces spans rather than a headcount — who was there and for how long, down to the minute. Your school sets what counts as attending, and the sum behind each verdict is printed beside it, so the parent or the inspector who disagrees with one can be shown what produced it.
Somebody who dropped out and rejoined has both spans, and the total is the total.
The words it uses in front of a young person
Sharing a picture that disappears is the one feature here that had to be built around the risk rather than the appeal: it is off until a school turns it on, never runs between staff and the people they are responsible for, and a copy is kept for thirty days that only the safeguarding officer can open — only on a report, and never without a record of who looked.
The parts that matter most to you
Out of about a hundred. Each one has a page saying what it does and what it will not do.
Safeguarding
Access to sensitive material is possible, recorded, and impossible to do quietly.
A log of what was done
Every moderation action, role change and integration change, with who did it — and the database refuses to let it be altered.
Moments
Off unless the organisation turns it on, never between staff and a member, sealed at rest — and reportable, which is the whole reason it is built this way.
A register nobody takes
Who was there and for how long, down to the minute they arrived and the minute they left.
Present, late or absent — by your rule
Your organisation decides what late means and what counts as attending. The arithmetic behind every verdict is printed next to it.
Who may do what
Owner, administrator, host and member — checked at the door, in the page, and in the database, rather than only in the menus.
People with no account
Open the meeting to guests, copy a link, and close it again — all from inside, while the person you are trying to let in is still waiting.
It looks like yours
Your logo on the way in, your accent colour through the product, and your own backdrop behind everybody in a meeting.
What you can ignore
The API, the webhooks and the broadcast studio are built for organisations with somebody to point at them. If that is not you, none of it is in the way.
Not quite you?
Tell us how your organisation actually runs
We will answer with what this would look like for you — which parts you would use, which you would never touch, and what it would take to connect it to what you already have.
info@seeuall.com