TS24 Rider Note
Privacy Policy
Last updated: August 5, 2026
1. Data We Collect
Account information: Email address and display name, collected when you create an account via Supabase Auth, and the interface language you use, so that service messages can be written in it.
Riding data: Session records, tyre pressures, suspension settings, lap times, and feeling scores. This data is stored locally on your device by default.
Payment information: Subscription status and transaction records processed by Stripe. We do not store your card details.
Usage data: Aggregate counts and timestamps only — how many sessions you have saved and when you last used the app. We do not collect circuit names, motorcycle details, tyre data, pressures, setup values, lap times, comments or tags as usage statistics.
Guidance interaction records: Only if you switch on optional guidance. See section 5 for exactly what is and is not stored.
Error reports: Anonymised diagnostics via Sentry.
2. How We Use Your Data
To provide and improve the riding data logging service.
To process subscription payments and manage your account.
For Factory Rider review: session data you explicitly upload is reviewed by the TS24 engineering team to provide personalised feedback.
To evaluate and improve the reviewed technical notes behind optional guidance — that is, to see whether a given note was actually useful, and to count how many distinct riders reported a comparable pattern before we ever describe something as common.
3. Legal Bases for Processing
Where the GDPR applies, we rely on the following legal bases.
Performance of a contract: creating and operating your account, providing the Service, and processing payments.
Consent: optional guidance and its interaction records, Factory Rider review uploads, and private cloud backup. You may withdraw consent at any time, which stops future processing but does not affect processing already carried out.
Legitimate interests: keeping the Service secure and reliable, and understanding aggregate usage at the level of counts and timestamps.
Legal obligation: retaining transaction records where tax or accounting law requires it.
4. Local-First Architecture
TS24 Rider Note is built local-first. Your riding session data is stored on your device using IndexedDB (via Dexie.js). We cannot read it.
There are exactly four exceptions, and each one is something you turn on or choose to do:
Private cloud backup: When you are signed in and the Private Cloud Backup toggle (Rider → Account) is on (default), we save a copy of your Rider Note database to your TS24 account so a browser data wipe (Safari ITP, clearing site data, switching devices) does not lose your history. Only your authenticated TS24 account can read these backups (Postgres Row-Level Security plus TLS in transit and Supabase at-rest encryption). We keep up to 5 versions and never read the contents on our side. You can disable the toggle at any time, or delete every backup from your account via the same screen.
Factory Rider review: session data you explicitly upload for review.
In-app feedback: the free-text message and language setting you voluntarily submit.
Optional guidance: described in section 5.
Outside these four, setup values, lap times, circuit names, and other session data remain on your device and are not transmitted.
5. Automated Guidance and AI Processing
The Rider Brief is generated entirely on your device from data you already saved. Nothing is sent anywhere to produce it, and it works offline.
Optional guidance is different, and it is off until you switch it on. When you use it, the words you wrote are converted into standardised category labels — for example a symptom category and a corner phase — and those labels are matched against technical notes that TS24 has reviewed and approved. Where a large language model is used to help with that conversion or with phrasing, the request is processed by Anthropic (anthropic.com) and is not used by them to train models.
What we store: the standardised labels, which reviewed notes were shown, the outcome, your account identifier, and the version of the consent you gave.
What we never store from guidance: your own wording, circuit names, motorcycle details, tyre brands, pressures, suspension or geometry values, lap times, or any free text.
No automated decision-making: guidance has no legal or similarly significant effect on you. It does not decide anything about your account, your access, or your safety. It is informational, a human being decides what to do with it, and section 8 of the Terms of Service sets out its limits.
You may withdraw consent at any time. Withdrawal stops future guidance processing, and on request we delete the interaction records already stored.
6. Third-Party Services
Supabase (supabase.com): Authentication and optional cloud data storage. Hosted in the EU (eu-central-1).
Stripe (stripe.com): Payment processing. Card details are handled solely by Stripe and subject to their privacy policy.
Anthropic (anthropic.com): Language model processing for optional guidance only, and only if you switch it on.
Sentry (sentry.io): Anonymised error monitoring to improve reliability.
Vercel (vercel.com): Application hosting, served from the EU (fra1).
Resend (resend.com): Sending account and service emails.
Each provider’s own privacy policy applies to the data it processes.
7. International Transfers
Our application hosting and database are located in the European Union. Some processors — including Anthropic, Stripe, Sentry and Resend — may process data outside your country, including in the United States.
Where personal data is transferred out of the European Economic Area, that transfer is covered by the European Commission’s Standard Contractual Clauses or another lawful transfer mechanism offered by the processor.
8. Data Sharing
We do not sell, rent, or trade your personal information. Your riding data is never shared with advertisers or data brokers, and is never shown to other users.
Any aggregate pattern we may publish inside the product is anonymised, is only ever produced from a minimum number of distinct riders, and never allows an individual to be identified.
9. Data Security
All data in transit is encrypted using HTTPS/TLS. Account data stored in Supabase is protected by Row-Level Security policies and encrypted at rest. We follow industry-standard security practices.
10. Your Rights
You have the right to access your personal data, to have it corrected, to have it erased, to restrict or object to processing, to receive it in a portable format, and — where processing is based on consent — to withdraw that consent at any time.
To exercise any of these, contact us at the address below. We will respond within 30 days.
If you are in the European Union or the United Kingdom, you also have the right to lodge a complaint with your national data protection authority. If you are in Japan, your rights under the Act on the Protection of Personal Information apply.
11. Data Retention
Account data is retained as long as your account is active. Upon account deletion, cloud data is purged within 30 days. Local device data must be cleared manually via your browser settings.
Private cloud backups: up to 5 versions, replaced as newer ones are made.
Guidance interaction records: kept linked to your account for 12 months. After 12 months the account identifier is irreversibly removed and only the anonymous standardised labels remain, so the reviewed notes can still be evaluated without the record pointing back to you. If you withdraw consent or delete your account, the linked records are deleted within 30 days.
Transaction records are retained for as long as tax and accounting law requires.
12. Cookies
We use a single authentication cookie to keep you signed in, and one for the Review Portal. No advertising or tracking cookies are used.
13. Age Requirement
The Service is not directed to children. You must be at least 16 years old, or the minimum age of digital consent in your country if that is higher, to create an account. If you believe a child has created an account, contact us and we will delete it.
14. Changes to This Policy
We may update this Privacy Policy from time to time. The updated date at the top of this page indicates when the policy was last revised. Where a change materially affects how we process your data, we will tell you before it takes effect and, where the law requires consent, ask for it again.
15. Contact
For privacy-related questions or data requests, contact: suzuki1344@icloud.com