Security
v0.1-draft · last reviewed 15 September 2026
Working draft. This page says how Clarvyn intends to operate. It has not been reviewed by a Ghana-qualified lawyer, and the wording will change when it is. We publish it now because a school deciding whether to trust us with children’s records should be able to read what we claim to do. Tell us where it is wrong: support@clarvyn.ai.
Schools are kept apart in the database, not by a filter
Every school gets its own PostgreSQL schema. A query runs inside one school’s schema and cannot name another’s, so cross-school access is not something a missing check in application code can leak. It is the strongest property this system has and it is why it was built this way.
Who can sign in, and how
- School staff sign in to the console with an email address and a password, set through a one-time link the school sends.
- Parents sign in to the app with a one-time code sent by SMS to the number the school holds for them. There is no parent password to leak.
- Roam Labs staff hold separate platform accounts. Platform-level actions are written to an audit table that survives the school being removed.
Within a school, what a member of staff can see follows the role the school gave them. A teacher sees the classes they teach.
In transit
Every connection to the website, the console and the apps is over HTTPS.
Reporting a vulnerability
Write to support@clarvyn.ai with enough detail to reproduce it. We will confirm we have it, tell you what we found, and tell you when it is fixed. Please give us a reasonable chance to fix it before publishing.
We do not run a paid bug bounty. We will not pursue anyone who reports a genuine finding in good faith and does not access, alter or keep other people’s data while doing so.
If something goes wrong
If a school’s data is exposed, we tell that school. We have not yet fixed a notification window in hours, and will publish it here when counsel review settles it. See data protection.