Trust & security
Security you can hand to your board.
Focus is built for districts that answer to auditors, unions, and parents. Governance is designed into the architecture — not bolted on.
Focus is built for districts that answer to auditors, unions, and parents. Governance is designed into the architecture — not bolted on.
The less a system holds, the less there is to defend. Focus collects only what enforcing policy and proving compliance requires.
Device enrollment identifiers, campus/schedule state, and policy events (what policy applied, when). Location is stored only per the org Monitoring policy — by default, only during an active lockdown.
No browsing history, no message or photo content, no keystrokes, no app content.
Compliance events are retained for your reporting period and then purged. Enrollment records end when a device is unenrolled.
All traffic uses TLS; data at rest is encrypted with industry-standard AES-256.
Admins sign in through your identity provider. Least-privilege roles separate district admins, school admins, and teachers.
Every policy change and lockdown is recorded, attributed, and exportable — the auditability our philosophy demands.
Focus adds a control layer without taking over device management, so your existing security posture stays intact.
Where we are today — stated plainly, because overstating certification is itself a security risk.
Type II audit in progress. We can share our current status and timeline under NDA during evaluation.
Built to support FERPA and COPPA obligations; we will sign a district data-privacy agreement (DPA) as part of onboarding.
A current subprocessor list and data-residency details are available on request for security review.
Certifications and audit status are stated as of this page's publication and confirmed in writing during procurement.
Request our security packet — architecture overview, subprocessor list, and DPA template.
Request the security packet →