Verified before they're public
A teacher's profile only goes live after we check their identity, credentials, and signed agreements.
Here's what the platform protects, and how it behaves when something goes wrong.
A teacher's profile only goes live after we check their identity, credentials, and signed agreements.
Anything you upload is checked for malware before it's shared, and every download is logged.
Lessons happen in our own classroom, single-use access only, with no recording in this release and a clear way to report a problem.
A real person on our team reviews every proposed teacher before you see it — never an automated match alone.
If a required service is down, that feature simply pauses with a clear message — we never fake a payment, scan, or verification result.
Every sensitive action is recorded and traceable, so a retried request or a mistake can always be reviewed and put right.
This separates pilot readiness from full commercial launch readiness.
Available now for learners aged 16-18, without teacher messaging or live classrooms.
Adults can submit precise requests, and operations reviews them before proposing any teacher.
5 real public teacher profiles live now; no fabricated profiles fill the directory.
Intentionally deferred until Stripe review, commercial terms, and live exercises are complete.
Not available yet; waiting on legal review, guardian linkage, and enhanced background checks.
Provider details, secrets, and internal system status remain available only to authorized operators.
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, and eligibility checks have passed operational review. Two-step verification is recommended for teachers and required for administrators.
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.
Current status: pilot configuration present. 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.