Plain-language pilot disclosure
Your data & privacy
The student pilot must remain closed until the privacy, consent, age-assurance and retention plan has been reviewed for the intended cohort.
What Clarity stores
Account, preferences and learning evidence
Your email, email-verification time, display name, password hash, target, learning goal, assessment date, weekly availability, access and voice preferences, login-session times, device description and keyed pseudonymous network identifier, lesson reflections, independent-check outcomes, mastery signals and next-review dates are stored in Clarity’s PostgreSQL database. Literal client IP addresses are not retained in new session records.
How sign-in works
Your password is not stored
Passwords are protected with Argon2. Your browser receives an HTTP-only session cookie; the database stores only a one-way hash of its random token. Changing your password signs out other sessions.
Account email
Verification and recovery links
Clarity stores only one-way hashes of short-lived, single-use verification and password-reset tokens. The configured transactional-email provider processes your address to deliver those links; production provider terms and retention must be included in the approved data inventory.
Adaptive AI mode
Some lesson text may go to OpenAI
When the operator enables adaptive mode, questions and bounded lesson context may be processed by OpenAI. Clarity sends a privacy-preserving safety identifier and asks the Responses API not to store application state. The production key must remain off until the approved OpenAI project and endpoint-retention controls are documented.
Your controls
Edit, export or delete your record
Signed-in learners can edit their learning setup, download their account, preferences, active-session metadata and learning record as JSON, or permanently delete it from Account. Operational backups require a reviewed retention and deletion procedure before a student release.