Security controls that are built and running
This page lists only controls that exist in the product today. Accreditation records are evidence, so the platform is built so that nothing is silently changed and nothing is ever erased.
The controls
Each of these is part of the running product.
Two-factor sign-in
Authenticator-app codes with recovery codes. An approver unit can require two-factor for everyone who holds a role in it.
Single sign-on
SAML single sign-on with your own identity provider, plus Google and Microsoft sign-in. Two-factor still applies to anyone enrolled.
An audit log on every write
Every change records who made it, what changed, when, and from where. The audit trail is append-only.
Tenant isolation
Each approver unit's data is separated at the query layer, and the test suite deliberately tries to read across that boundary.
Encrypted secrets
Provider payment accounts, AI credentials, reporting-body, Zoom, SMS, LTI and xAPI keys, and two-factor secrets are encrypted in the database. Passwords are stored only as one-way hashes.
Bring your own AI key
AI features can run on your own model-provider key, so application text is processed under your own agreement with that provider.
No hard deletes
Records are never erased. Deleting something removes it from view while keeping it on the record, and every change is in the audit trail.
Signed verification
Verification results are signed with Ed25519 and the public key is published, so a result can be checked independently.
Backups
Nightly backups of the database and uploaded files, with a written restore procedure.
Certifications
We have not completed a SOC 2 audit or any other third-party security certification, and we do not claim one. If your organization’s review needs a security questionnaire answered, ask us and we will answer it accurately.
To report a security concern, contact us.
Questions from your security team?
Send them over. We will answer with what is built, and say plainly what is not.