Data used for diagnostics
The app can store answers, scores, skill breakdowns, mistake reviews, speaking or writing feedback, test history, report links, email restore requests, and attribution events needed to understand product flows.
Privacy
Last updated May 20, 2026. This page explains the product data used to save reports, personalize practice, restore profiles, and improve diagnostic flows.
The app can store answers, scores, skill breakdowns, mistake reviews, speaking or writing feedback, test history, report links, email restore requests, and attribution events needed to understand product flows.
Some history is stored in the browser so users can keep reports on the same device. When server routes are available, saved reports, review sessions, profile data, email requests, payment access records, and attribution events can also be written to local server storage.
If a user enters an email, the product can use it to connect report access, send or queue restore links, and reconnect saved reports to a browser. Report restore links should be treated as private.
Speaking and pronunciation tasks may use browser speech capture or server transcription when the user records audio. The app uses that evidence to create feedback such as transcript, clarity, target-word match, timing, and confidence notes.
Checkout, transcription, text generation, image generation, and audio generation may depend on configured third-party providers. Provider availability and data handling depend on the environment variables and integrations active in the deployment.
Users can clear browser history from the results page and request report restore by email. Operational records may remain in server-side local storage when generated by API routes, checkout events, or admin analytics.