Your information

Privacy starts with clarity.

This notice explains the foundation’s intended data boundaries and the difference between demonstration and connected use.

Foundation notice · policy draft. The operator’s identity, contact details, hosting region, retention periods, and request process must be finalized before an operational public release. This is not a finalized public privacy policy.

Demonstration mode

The demonstration contains no supplied learner records, practice attempts, or scores. Theme preferences and profile preferences you explicitly save in the demonstration may be kept in this browser. They do not create a Supabase account or a real study record.

Use the browser’s site-data controls to remove locally saved preferences. Do not enter sensitive personal information into a demonstration profile.

Connected accounts and profiles

When the owner configures connected mode, Supabase provides authentication and stores the profile fields you choose to save, such as display name, study goal, exam date, and target band. Google authentication is optional and requires a separately configured Google sign-in provider.

Private enrollment limits access to authorized accounts. Profile access is controlled by ownership policies. Administrative access requires additional authorization and multi-factor authentication.

Essays, recordings, and AI

This foundation does not collect practice essays, handwriting uploads, or speaking recordings, and does not send work to an AI model. Those features are not available yet.

The specification requires private storage and separate, explicit consent before any future reuse of a learner’s work for training. Training-data reuse is not enabled in this release.

Essential storage and security records

Connected sign-in uses authentication cookies to maintain a session. Browser storage can hold interface preferences. The foundation also prepares security-event records for account and administrative activity; these are separate from study results.

The hosting and authentication providers may process technical request information when a connected site is deployed. The operator must document the selected providers and their applicable settings before public use.

Retention, export, and deletion

Operational retention periods, backup expiry, and a verified contact route are not yet defined. Automated account export and deletion are planned beyond this foundation. The operator must establish a request process and publish these details before collecting information from public users.

For the current private release, contact the person who provided access regarding account information. A public support address has not been supplied.

Questions about this release

Read the frequently asked questions for the current feature boundaries, or the foundation terms notice for the intended use of this project.