1. Who is responsible
Proposed operator: Dylan Titley, United Kingdom. The final legal service operator and data controller must be confirmed before public registration opens. A data controller decides why and how personal information is used.
Privacy questions, requests or complaints: [CONTACT EMAIL — TO BE ADDED BEFORE PUBLIC LAUNCH]
The contact details and responsibility review must be completed before this notice becomes final.
2. Privacy in plain English
- Your study records are not published as a profile or shared with other ordinary Stride accounts.
- We use Supabase for accounts and cloud study records. The project region is Paris, France, as confirmed by the project owner.
- Stride has no advertising, paid plans, marketing emails or optional visitor-tracking analytics at launch. Hosting and account providers still handle operational and security information.
- You can export study data. Account deletion needs a working contact process before public launch.
- Signing out does not erase every local copy. On a shared device, clear Stride’s browser storage and protect any backup files.
Stride is intended for people aged 13 and over. You can ask a trusted adult to help you understand this page.
3. Information the current website handles
| Information | How it is used |
|---|---|
| Email, internal account ID, password submitted for sign-in, verification and session information | Create and verify an account, sign in, refresh the session and reset a password. Supabase handles authentication; the study-data table does not store passwords. |
| Approved signup addresses, enabled/disabled approval and date added | Restrict new-account registration for the friends trial. Addresses are supplied privately by the project owner, rather than obtained from other users’ contact lists. |
| Name entered during signup | Stored in the account profile. The tracker does not currently use this field elsewhere; its necessity is under review before public launch. |
| Subjects, colours, goals, study dates and minutes, activities, topics, notes, question marks, plans, deadlines and completion states | Save your study space, synchronise records and calculate the progress you ask to track. |
| Course/provider names, course and certificate links, module progress and personal reward targets | Organise independent learning and your own incentives. |
| Device/browser request details, IP addresses, authentication events and service logs | Deliver the website, process account requests, investigate faults and protect access. The providers receive these as part of their services. |
| Messages you choose to send to support | Respond to your question, request or complaint once the public contact route is active. |
Information comes from what you enter or import, your browser’s requests, and the account service. Signup approvals also come from the project owner’s private list. Other ordinary users cannot read that list. The approved-email rule has been prepared in code and becomes active only after its Supabase hook is installed and enabled. Study totals and achievements are derived from your records. The focus timer does not monitor your activity in other apps or websites.
We do not ask for a school address, precise GPS location, identity documents or payment details. Free-text fields can still contain sensitive information if you type it; please keep it out of Stride.
4. Why information is used and the proposed legal grounds
The following grounds are proposals for the final controller to review and document before public registration. Agreement to Terms is not being treated as blanket consent to process personal information.
| Purpose | Proposed UK GDPR ground |
|---|---|
| Provide the private account and study-tracking functions you request; protect unsynced work | Legitimate interests in providing a requested study-organisation service, subject to a necessity and balancing assessment that gives particular weight to children’s rights. |
| Protect accounts, investigate faults and respond to support | Legitimate interests in secure, reliable operation and resolving users’ requests, using only information needed for those purposes. |
| Meet a specific legal duty, including applicable rights requests | Legal obligation, where that duty actually applies. Information will not be retained merely because it might be useful. |
If an optional feature later relies on consent, its purpose and choice must be explained separately before it is used. This draft does not authorise future advertising or analytics.
Account information is needed to sign in and save online records. Some study fields are optional. The required name field needs a minimisation decision before launch.
5. Who receives information
- Supabase: authentication, study-data hosting, operational logs and verification/reset email delivery. Authorised project administrators and provider personnel may have access where needed to operate or support the service. Account access controls do not make records end-to-end encrypted against the operator.
- GitHub Pages: currently hosts the website files. GitHub states that visitors’ IP addresses are logged for security. Study records are saved to Supabase rather than committed to the public code repository.
- jsDelivr: currently delivers the Supabase browser library. Loading it sends a network request, including an IP address and browser request information, to its delivery infrastructure.
- Email services: verification/reset messages pass through the configured sending service and your email provider. A production sending provider has not yet been selected.
We may disclose information when a valid legal requirement applies or where necessary and proportionate to establish or defend legal rights. Stride does not sell study records or disclose them to advertisers.
Before launch: confirm suitable hosting for account sign-in, the production email provider, and provider/data-processing arrangements. Update this list if the current setup changes. Google and Apple sign-in are not enabled.
Provider information: GitHub privacy, Supabase legal resources, and jsDelivr privacy information.
6. Where information is processed
The project owner has confirmed that the Supabase project is in Paris, France. That is the selected project region, not a promise that every service operation happens only in France.
Hosting, email delivery, support and security operations can involve other locations. Supabase describes region-specific database hosting alongside processing outside that region for certain platform operations.
[CONFIRM CURRENT PROVIDER LOCATIONS AND APPLICABLE INTERNATIONAL-TRANSFER SAFEGUARDS BEFORE PUBLIC LAUNCH]
The final notice must explain the safeguards actually applicable to this deployment and how to obtain information about them. We have not assumed that choosing Paris alone resolves every transfer issue.
7. Browser storage and your choices
The current account website uses browser local storage as well as its online database. This section also covers cookies or similar technologies if the account or hosting infrastructure uses them.
| Storage | Purpose and duration |
|---|---|
| Supabase authentication session | Keep you signed in and refresh access. The account library manages its lifetime and removes the local sign-in session on successful sign-out. Other devices’ sessions are not automatically signed out. |
Account-specific study copy (stride.draft.<account ID>) | Hold a saved or unsynced copy for recovery. It has no automatic expiry in the current code and can remain after sign-out until overwritten or cleared. |
Theme preference (stride.theme) | Remember light or dark mode. It currently has no automatic expiry. You can switch theme in Stride or clear this browser setting. |
Older browser-only records (stride.v1), if present | May remain from the earlier tracker. They are not automatically imported into an account; you choose whether to import a backup. |
You can clear storage in your browser’s site-data settings. Export anything you want to keep first: clearing storage can sign you out and erase unsynced work. Downloaded backup files remain under your control and are not removed by signing out.
Necessary account/storage functions need a documented assessment of the applicable device-storage rules. A persistent appearance preference also needs clear information and an easy way to object to remembering it.
Before launch: provide the theme-storage opt-out and decide whether local study copies should have an expiry or user control. We are not claiming that every local-storage use is automatically exempt from consent requirements.
8. Retention and deletion
Current test behaviour: online records remain while the account exists, unless records are replaced or removed. There is no automatic unverified-account, inactive-account or support-mail cleanup schedule in the website yet. The new approval list also has no automatic expiry: disabled approvals remain until the owner removes them. Disabling approval prevents a new signup once the rule is active; it does not delete an existing account. Approval-row retention and removal on request need a defined process before the friends trial opens.
Proposed schedule for review — not yet active:
| Information | Proposed limit |
|---|---|
| Unverified accounts | Remove after 30 days from creation if verification is not completed. |
| Verified account and study records | Keep while the account is in use or until a valid deletion request. After 24 months without sign-in or saved activity, give 30 days’ notice before closure; renewed activity stops that closure. |
| Support correspondence | Remove 90 days after the issue is resolved, unless a specific legal duty or unresolved legal claim requires a documented exception. |
| Logs, provider backups and email-delivery records | Exact provider/configuration limits must be confirmed before launch. Removing a live record does not necessarily remove every recovery copy immediately. |
A deletion request needs identity/authority checks and a process for removing the live account and associated study row. Provider recovery copies must expire under a defined schedule; any restored backup must have requested deletions reapplied. Narrow legal exceptions must be explained rather than used to keep everything indefinitely.
Deleting online data cannot erase backup files you downloaded or browser data on devices we cannot access. Clear those separately when appropriate.
9. Young users and safe defaults
The minimum intended age is 13. Because teenagers will use Stride, their privacy needs must be considered in the service design, not just in this page. The current tracker has no public profiles, leaderboards, messaging between users, advertising or precise-location feature.
Use a nickname rather than private identifying details if a name field is retained. Do not record sensitive details about classmates, family members or people discussed in your coursework. You can ask a trusted adult for help with a privacy request.
A parent or guardian can raise a concern about a child’s information. We must check identity, authority and the young person’s rights before sharing records; a relationship alone does not automatically give access to every entry.
Before launch: complete the children’s privacy/risk assessment, justify the age-assurance approach and remove unnecessary registration information. If an under-13 account is identified, a proportionate restriction/deletion process is needed.
10. Your choices and rights
You can ask for a copy of your information, correction of inaccurate information, deletion, or limits on its use. Some rights have conditions or lawful exceptions. A legal right to data portability applies where its conditions are met; Export backup also gives you a copy of study records as a product feature.
You can object to a use based on legitimate interests. We must consider your circumstances and stop that use unless the law permits us to continue for a stronger reason. Contact us through the privacy route above.
Export backup contains study records and settings; it is not a complete copy of the separate authentication profile or provider logs. Contact the controller if you need those as part of a rights request.
Requests normally require a response within one month under UK data-protection law. Any lawful extension, necessary clarification or identity check must be explained. The public contact route and request-handling process must be operational before launch.
Stride calculates totals, levels and graphs from what you enter. It does not use those calculations to make decisions with legal or similarly significant effects on you.
You can also complain to the UK Information Commissioner’s Office (ICO). Contacting us first may help resolve a problem, but does not prevent you contacting the regulator.
11. Changes to this notice
We will show a new date and version when the notice changes, and explain material changes before a new use of information begins where required. A new domain, host, email provider, social sign-in option, advertising or analytics would require a fresh review of these details.
For the rules of using Stride, read the separate Terms & Conditions. Neither document is final while its draft notice or unresolved placeholders remain.