Skip to content
Security and privacy

Built to keep children’s records safe

Children are on Brim, so the controls are part of how it is built. Each section below shows one of them and how it works.

Request a demo
Encryption

Sealed so only the right person can read it

Messages between parents and children are sealed end to end. The server keeps only a sealed copy. Health and safeguarding records are sealed to the role that needs them, so neither the school’s IT staff nor Brim staff can read them. The master key is split between several officers, and no password sits in a settings file.

  • Family messages are sealed end to end
  • Health and safeguarding records are sealed to a role
  • Any three of five officers can rebuild the master key
123453 of 5 · sealed

The master key is split into five shares held by separate officers. Any three reconstruct it. One person alone can do nothing, and that includes every Brim engineer.

Who can do what

Each person sees only their own work

Each role carries the permissions your school gives it, instead of one admin and everyone else. Sensitive actions need two people to sign. Brim checks that the person who raised a payment is not the one who approves it. The rules bind the school’s admin too.

  • Permissions your school sets for each role
  • Two people sign every sensitive action
  • The person who raises a payment cannot approve it

A. Nakato

posts the entry

B. Mukasa

approves it

A. Nakato cannot approve her own entry. That refusal comes from the database itself.

Artificial intelligence

AI that helps without seeing the child

Brim uses AI to draft lesson summaries for parents, suggest hints from your syllabus and read handwriting. Each AI feature stays off until your school turns it on. Before any text reaches the AI, names, learner numbers and contacts are swapped for placeholders. Brim puts them back, and a person reviews the draft before anyone sees it.

  • Names and contact details are removed before the AI sees the text
  • Every AI feature is off until your school turns it on
  • The AI drafts and a person decides

On Brim

Nakato Sarah

S5 East · #S24-5892

Sent to the model

⟨student⟩

S5 East · ⟨id⟩

Names, numbers and contacts are swapped for neutral placeholders before anything reaches an AI model. It sees the shape of the question and nothing of the child.

The record

A record you can always show

Every action that matters goes into a log nobody can edit. A broadcast, a released mark, an opened safeguarding case and a look at a sensitive record all go in. Each entry carries a fingerprint of the one before it, so any change shows.

  • Entries are added and never changed
  • Looking at a sensitive record is logged as well as every change
  • Each entry names who acted, when and with what permission
1broadcast.sentsha2569f2a…2grade.releasedsha256c41b…prev 9f2a…3case.openedsha2567e08…prev c41b…verifies

Each entry carries the hash of the one before it. Remove or alter a link and the chain stops verifying. Tampering shows.

Hosting and messaging

Each school kept apart

Brim runs on Cloudflare’s network, with no long-running server open to the internet. The database checks the school on every request, so one school can never read another school’s records. Text messages and short codes reach any phone through Africa’s Talking.

  • No long-running server to break into
  • Every request is checked against its own school
  • Text messages and short codes for homes with a weak connection
SELECT … school ACloudflare edgethe Worker, so there is no app server to breachNeon Postgresrow-level security · enforced every queryschool A rowsschool B · blockedAfrica’s TalkingSMS and USSD to any phone

The database checks the school on every request. One school can never read another school’s rows.

Tablets at the gate and the Station

Tablets you can trust at the gate and in the school

The gate tablet finds a learner by face when they report. At the Station inside the school, a PIN finds the learner and the face or fingerprint confirms it is them. Each template is sealed with a key for your school alone and deleted when your school no longer needs it. A tablet reported stolen locks at once, stays locked after a restart, reports where it is and takes photos of whoever holds it.

  • Templates are sealed with your school’s own key
  • At the Station, a PIN alone opens nothing
  • A stolen tablet locks itself and reports where it is
Reported stolenStation 3 · 14:06
1

Lock

Instant, persists across reboot

2

Locate

GPS ping reported home

3

Recover

Covert capture for evidence

Recovery

Recovery that has been practised

Role keys are copied every week, sealed under the master key and kept off-site with a check code. A copy is proven before anyone relies on it. A written recovery plan is practised once a year.

  • A sealed copy of the keys every week, kept off-site
  • Each copy is checked before it is trusted
  • A written plan and a practice restore every year
SundayEncryptOff-siterestorable

Role keys are snapshotted weekly, encrypted under the master key and stored off-site with an HMAC tag. The disaster-recovery restore is rehearsed.

What Brim will not do

No badge Brim has not earned

Brim claims no certificate it does not hold. Nobody at Brim reads a family’s private messages, for safety or for any other reason. Your school runs its own channels, and each family keeps its words to itself.

Who can read which records, drawn

Sealed disclosure

encrypted at rest

DSL’s key

the only key that opens it

Not even IT or platform staff hold the key. Every open is written to a read trail.

Ask Brim anything about security

If you check suppliers for your school, ask how Brim protects your records. The Brim team answers by phone or email.

Or write to brim@nacre.systems