Private learning materials
Files upload directly into quarantine, are malware-scanned, and are released only after a clean result. Every download is authorized and audited.
This page explains what the platform protects and how it behaves when something goes wrong. Provider details, secrets, and internal system status remain available only to authorized operators.
This status confirms that required configuration is present; it does not claim that every provider has passed a live transaction. Operational readiness is granted only after a successful exercise is recorded for every critical journey.
Files upload directly into quarantine, are malware-scanned, and are released only after a clean result. Every download is authorized and audited.
Teacher profiles are not published until identity, credentials, agreements, MFA, and eligibility checks have passed operational review.
Classroom access uses short-lived participant tokens, attendance events, explicit reporting controls, and no lesson recording in the initial release.
Protected features stop with a clear error when a required provider is unavailable. The platform never fabricates payment, scanning, or verification results.
Payments, checkout retries, and webhook deliveries are keyed to idempotency identifiers, so a repeated or duplicated request cannot double-charge a learner or double-record an event.
Every sensitive action — teacher approvals, booking changes, refunds, incident handling — is written to an append-only audit log with the actor, before and after state, and a timestamp.