Security & Privacy
Student data is the product we protect, not the product we sell.
How ConductKeeper protects student data — clear answers to the questions your IT director will ask.
Tenant isolation at the data layer
Every school runs on its own subdomain, and every query is automatically scoped to that school — enforced in the platform’s data-access layer, not left to application code to remember.
FERPA audit trail
Access to student records is logged — incident actions, data access, exports, and configuration changes — indexed by student, user, and incident.
Enterprise sign-in
SSO through your existing identity provider (Azure AD, Google, Okta, Auth0), with SCIM v2 provisioning so access follows your directory — including offboarding.
Role-based access
Permissions drive both the API and the interface; staff see only what their role allows, and students see only their own record.
AI with guardrails
Every AI call is logged with model, token counts, and estimated cost, and each school can cap usage. An optional strict-privacy mode pseudonymizes student identities in everything sent to AI models — the model reasons about “Student A”; real names are restored only inside your school’s session.
Public displays, private data
Hallway leaderboard links are IP-restricted to your campus network, so celebration screens work at school and nowhere else.
Questions about hosting, backups, or data processing?
Ask us directly — you’ll get an engineer, not a form letter.