Security & privacy
How Pideia protects your school's data
A school trusts us with children's records. This page sets out exactly how we look after them — specific mechanisms you can hold us to, not reassuring adjectives.
Isolation and access
Every school sealed off
Row-level security is enforced by the database on every school table, scoped to membership and role. A query for another school's rows returns nothing.
Each role sees its own slice
A student, a parent, a teacher and a principal see different things because the database decides what each may read — not because a screen hides a button.
Several campuses, still separate
Someone who belongs to more than one school switches between them with one login. Switching never lets one campus read another’s records.
Support access is audited and scoped
Our team supports schools through an internal console split into roles, so staff reach only what their job needs — and every action there is logged with who did it and when.
Children's privacy
Consent from a parent, not a child
A student under eighteen cannot record their own consent to the privacy policy; Pideia waits for a parent's. From their eighteenth birthday, their own consent counts.
Feelings stay private
A parent sees how their child is feeling in Wellness Wave — the mood, never the private note. Counsellors see check-ins only when the school grants them access.
Recordings stay with their class
Lesson recordings are staff-only, with one exception: a recording of a scheduled class call is visible to that class's students, and to nobody else.
No self sign-up
Every account in a school is created by that school. There is no public signup and no shared school code that could admit a stranger.
Online classes
Private rooms
Pi-Meet rooms are created privately on our server. The browser never holds the key that creates them.
A pass for each person
Every participant is issued their own short-lived pass, so a link forwarded to a WhatsApp group admits nobody.
A register of who joined
Every pass issued is logged, so the school can see who was let into a class and when.
Your rights over the data
Your school is the data fiduciary
Under the Digital Personal Data Protection Act, your school decides what happens to its records. Pideia processes them on your behalf.
Thirty days to answer
A request to see, export, correct or erase someone’s data is answered within thirty days, and the clock is tracked.
Erasure means erasure
Erasing a person removes their records and the files attached to them, not only the rows that point at the files.
Retention set to your policy
How long each kind of record is kept can be set for your school on request, instead of one rule for everyone.
Infrastructure and transparency
Where your data lives
The database is hosted in Singapore (AWS, via Supabase). We would rather tell you plainly than let you assume.
Encrypted in transit and at rest
Every connection is HTTPS with strict transport security, and data is encrypted at rest by our database provider.
Hardened by default
A strict content security policy, no framing of our pages by other sites, and browser permissions limited to what a class call needs.
Every sub-processor, named
We keep a list of every service that processes school data and where it does so, and send it to any school that asks.
Questions schools ask about their data
Have a security questionnaire?
Send it to us. We answer vendor questionnaires from schools and trusts directly.
Ask us anything about your data
Bring your questions to a demo, or send them ahead. We would rather answer a hard question now than after you have signed.
Book a demo