What we hold, and what we don't
A school's roster — pupils, staff, classes — so that each person sees the right apps and the school can see how they are used. The school decides who is on it, and a roster sync never deletes a pupil on its own.
We don't hold pupils' work or marks. What a pupil does inside an app stays with that app.
What an app receives
When a pupil opens an app, the app receives a code that stands for the pupil — for example RB-4213 — and the school it belongs to. It never receives a pupil's name, email or date of birth.
The code is the same each time within one school, so the app can keep the pupil's progress, and means nothing outside it.
Usage: time only
EduSpaze Connect measures how long each app is open and in use, by class and over time — so a school knows whether what it bought is being used. It never records what anyone wrote, scored or looked at.
What parents see
A parent is linked to a child only when the school invites them, by an emailed link. They then see their own child's apps and the time spent in them, and can message the school. They never see prices, contracts or other children. More for parents
The audit trail, and erasure
Every change to a record is captured on an audit trail held in a separate service, apart from the platform, so it can't be quietly edited afterwards. A school can see who did what in its own account.
When a person asks to be erased — or leaves the school — their identifying details are removed, including from the audit trail, without breaking the record of what happened.
Where data is stored, and who processes it
EduSpaze Connect runs on Google Cloud, and its data is stored in Singapore.
We use AI services from Anthropic (Claude) and Google (Gemini) to improve the platform's operational efficiency.
Questions and data requests
To ask what we hold about you or your child, to correct it, or to have it erased, contact the school first — it decides what is on its roster — or write to us at connect@eduspazeconnect.com.
For IT leads
- Identity and single sign-on — every way a person signs in, and the codes an app receives
- Roster mapping protocol — what is shared with an app, and what never is
- Engagement tracking — how time in apps is measured
- Audit trail — what is recorded, and how erasure works
- School admin integration guide