course.host

Security & privacy

Security and privacy

The short version: each organisation's data is encrypted under its own key, reachable only through its own access boundary, and destroyed with that key when the account is deleted.

Separation

A key per organisation

Sensitive fields are encrypted with a key belonging to your organisation alone. Another organisation's credentials cannot decrypt them even with the ciphertext in hand.

Enforced by the platform, not by code review

Every request runs under credentials scoped to one organisation. A mistake in our code is rejected by the access rules rather than served.

Deletion means deletion

Closing an account schedules its key for destruction. After that, even our backups cannot be read.

Access

No passwords for learners

Learners sign in with a single-use link, valid for fifteen minutes. There is no learner password to steal or reuse.

Two-factor for administrators

Administrator accounts require an authenticator app. There is no self-service reset that an email compromise could exploit.

Sessions expire

Idle sessions end automatically, and signing out revokes the session everywhere.

Data handling

Canadian residency

Data is stored and processed in Canada (ca-central-1).

Minimal by default

We hold what a course record needs: who completed what, when, and with what score. Raw activity data expires after 90 days.

Audited access

Access to your data by our staff is recorded and visible to you.

Reporting a problem

Security reports are welcome and will be acknowledged. See security.txt for the current contact, or use the contact page.