Student data
Where student work goes, stated plainly
The honest version, including the parts most vendors leave out.
What we do
- Identifiers stripped Before any submission goes to an AI provider. The model sees the work, not the student.
- Isolated per instructor And per organization, enforced on every request by the application.
- An audit trail Who accessed what, plus automatic cleanup of temporary files holding student work.
- Deletion on demand A grading job and everything it produced can be purged.
- A fully local option Point it at a model on your own hardware and no submission leaves your network.
What we will not claim
There is no FERPA certification to hold, so we do not say we have one. Your institution should assess its own deployment, and we will hand over whatever detail that takes.
When a cloud provider is selected, de-identified submission content goes to it for evaluation. That is a real trade-off, which is why the local option exists, and it is set per function.
Database-level row security arrives with the move to PostgreSQL. Until then isolation is enforced by the application, and we would rather say so.
You choose where the AI runs
What leaves your network
Nothing
Good for
Programs with strict data rules, or work you would not send anywhere
What leaves your network
De-identified submission content, for that function only
Good for
Judgements that need a larger model, such as essay feedback
What leaves your network
Only what you choose to send to your own AI account
Good for
An instructor building a course alone
IT or compliance questions are welcome before a pilot starts.
Ask for a data review