Trust
Security overview
Updated September 2, 2026
School boundaries
Cohorvia isolates each school workspace and checks school, user, and role authorization on protected requests. A new school may receive reusable configuration templates, but never another school's students, grades, files, finance records, or messages.
Identity and access
Accounts are individual and role-based. Students are limited to their own authorized record, instructors to their assigned work, school administrators to their own institution, and Cohorvia platform-owner functions to a separate owner identity.
Application protection
The service uses encrypted transport, restricted browser policies, protected document delivery, validated provider webhooks, server-side secret storage, rate limits, and audit history for sensitive activity.
Monitoring and recovery
Cohorvia uses application monitoring, scheduled health checks, checksum-verified backups, and controlled restore rehearsals. Production onboarding also requires an independent backup path and a documented incident-response process.
Responsible reporting
Authorized users should report suspicious access through the in-product Help Center. Other security concerns can be submitted through the guided-demo form with “security report” in the message. Do not include student records or exploit data in the public form.
Scope
This is a plain-language summary of current engineering controls, not a claim of independent certification. Contractual security commitments and provider disclosures are supplied during customer review.