Data protection
Security
How a school's records are kept apart, encrypted and accounted for.
Last updated 13 September 2026
Security
Safe for your pupils. Simple for your staff.
Children's records deserve the highest care. REO360 is built so the right people see the right things — and nothing else.
Stored in India
Your school's records and backups stay in Indian data centres.
A database of your own
Every school has its own database, so one school can never see another's records.
The right access for every role
Teachers, accountants and parents each see only what their role allows.
Every action on record
Who marked, verified, published or downloaded — logged and visible to the school.
No passwords for parents
Families sign in with a one-time code sent to their verified mobile number.
Backed up every night
Daily backups, each one verified when it is made.
Draft for the rebuild. Every section marked below is placeholder structure and has not yet been reviewed by counsel.
1. Data residency
All production data, backups and logs are held in Indian regions. Support access is from India. No pupil record is replicated outside the country.
2. Isolation between schools
Each school's records live in their own database. On top of that, every table carries the school identifier and enforces row-level security, and the application connects with a role that cannot bypass it.
Isolation is tested per table in the build: for every tenant-scoped table there is a test asserting that school B can neither read nor write school A's rows.
3. Encryption
Traffic is TLS 1.3. Data at rest is encrypted by the storage layer, and sensitive columns are additionally encrypted with envelope encryption so a database dump alone does not disclose them.
Passwords and PINs are hashed with argon2id. One-time codes are stored only as an HMAC and are never logged.
4. Who can see what
Authorisation is a permission and a scope, checked together on every request. A subject teacher sees the sections they teach; a class teacher sees their class; a guardian sees the children linked to them and only the categories the school allowed; a pupil sees themselves.
Administrative, principal and finance contexts require a step-up to a second factor before they open.
5. Audit and accountability
Every read of a sensitive record and every change to one is written to an append-only audit log with the person, the context and the time. Financial records are never edited in place.
6. Certifications and third-party assurance
[to be reviewed by counsel]Independent audit, penetration-testing cadence and certification status are placeholder structure.
7. Reporting a vulnerability
[to be reviewed by counsel]Write to security@reo360.in with the detail needed to reproduce the issue. We acknowledge within one working day and will not pursue anyone who reports in good faith.
The formal disclosure policy and safe-harbour wording are placeholder structure.
See REO360 with your own school's data
A 30-minute demo with your timetable, fee structure and a section of your pupils loaded in. No commitment, no card.
