Built for the most sensitive records a school holds.
A threat assessment file can follow a child for years. This page says plainly what we store, who can see it, and how it is protected.
What we store
As little as possible. A student is in the system only if a Case has been opened about them. There is no roster import, so the other students in your district are never here at all.
Demographic fields are optional and off until your admin turns them on. Interview audio is never stored: dictation is processed on the staff member's own device, and only the text they review is saved.
Who can see a case
Each person gets a Role with a scope: the whole Organization, chosen Schools, or only the Cases they are assigned. Standard Roles are ready on day one and you can build your own.
A teacher asked for input is a Contributor and sees one Form, nothing else. A police officer or county clinician is a Case Guest and sees one Case, for a set number of days. Every read and every change passes through the same permission check, and repeated denied attempts alert your admin.
We cannot open your cases.
Our staff have no standing access to case content. If you need help with a specific Case, your admin approves a Support Access Grant: read-only, limited to the Cases and the hours you choose, shown with a banner, and every look written to your audit log.
How it is protected
- A database of your own
- Every Organization's records live in a separate database with its own encryption key. No query can reach across districts, because another district's data is not in the database being queried.
- Encrypted twice
- Everything is encrypted in transit and at rest. Narratives, interview answers, determinations and attachments are encrypted again inside the application with a key that belongs to your Organization, so a copied database file is unreadable.
- Searchable without being readable
- Names, student IDs and Case Numbers are found through keyed one-way search tokens. Search works, and the values are not stored in readable form.
- Stored in the United States
- Databases and files are kept in U.S. locations.
- Sign-in
- Staff sign in with their Google or Microsoft school accounts. Password sign-in always requires a second factor. Sessions end after inactivity.
- Files
- Uploads are virus-scanned before anyone can open them, visible only to people on the Case, and downloaded through short-lived links.
- Messages
- Emails and push notifications never contain a student's name or case details. They carry a heads-up and a sign-in link.
Every look is logged
Your admin can read and export the whole log.
FERPA and your agreement
No real student data enters the system until your Organization has signed the data privacy agreement, and the app blocks real Case creation until then. Trials run in a separate Demo Environment with its own database, storage and keys, holding fictional data only.
When information is shared outside the school under FERPA's health-or-safety exception, the Case records what was shared, with whom, and the threat that justified it. When a parent asks to inspect records, a single-student export produces everything held about their child, with other students' names redacted.
Your data is used to provide the service and for nothing else: no advertising, no model training, no sale.
No AI on student records
No AI reads, summarizes or scores case content. The app never calculates a risk score or a risk level. It reminds, prompts and records, and your trained team makes the judgment.
If something goes wrong, and when you leave
We keep an incident response plan with a target of notifying affected customers within 72 hours of confirming a breach.
You can export all of your data at any time. Retention is yours to set, and nothing is deleted automatically. Deleting records takes an admin plus a second approver, and a legal hold stops it. At contract end you get a read-only grace period, a full export, verified deletion with the Organization's key destroyed, and a certificate of destruction. If an account is suspended for non-payment you can still export your records.
Documents for your vendor review
Everything a privacy officer or technology director usually asks for.
- Data privacy agreementIn legal review
- Security overviewIn legal review
- Subprocessor listIn legal review
- Accessibility statementIn legal review
These documents are with our attorney and will be downloadable here when review is complete. Ask for a draft if your review can't wait.
Accessibility
This site and the app are built to WCAG 2.1 AA. Text meets contrast requirements, everything works from the keyboard, and status is never shown by color alone: every status carries an icon and a label.
A VPAT will be published before our first large-district sale. If you hit a barrier, tell us and we will fix it.