Privacy Notice
Last updated: 2026-09-12
This notice describes what Tire Pressure Predictor sends, what it does not, and what you can do about it. It is written to be read in full — it is short on purpose.
1. Controller
The data controller is Luca Villa.
For privacy questions or to exercise your rights: [email protected]
2. Scope
This notice covers Tire Pressure Predictor, account creation and sign-in, licence migration and renewal, usage reporting, referrals, optional feedback and Mobile sharing. Other MotorsportSoftware products have their own notices.
Telemetry, predictions, Session Logs and settings are normally stored on your computer. Each account has its own local data folder. Signing in on another computer does not upload or transfer this work automatically.
3. What the app reports
In account mode, TPP sends weekly usage counters linked to your account and a random installation identifier. These reports are identifiable, not anonymous. They include app version, starts, session minutes, processed runs, predictions, feature use and technical failures. Offline counters are sent when the app reconnects.
Earlier licence-key versions use a different format, which can include the licence key, registered customer name, user-chosen pair names, system information and activity timing. Existing licence history may be associated with the account that migrates that licence.
4. What stays on your computer
Account usage reports do not include telemetry contents, pressures, temperatures, lap times, track or driver names, vehicle/tyre pair names, file paths or free text. Sharing, feedback and exports are separate actions described below.
Infrastructure providers process network requests, including IP addresses and connection information, to operate and protect the service. Cloudflare performs bot verification for the website download and account operations. The website download does not require your name or email.
5. Names, backups and exports
Names you enter in Telemetry or Session Logs stay with those local records and are excluded from account usage counters. They may be included in a Mobile share, feedback screenshot or file that you choose to send.
Before licence migration or import of legacy data, TPP creates and verifies a local backup. It includes saved application data, settings and available linked telemetry sources. Missing source folders do not remove saved processed data; their links are retained and recreated as empty folders when restored. Backups are not uploaded automatically and remain on your computer until you delete them. A diagnostic export may also contain file paths and configuration: review it before sharing.
6. Sharing a session with your phone
When you choose Mobile sharing, TPP uploads the selected session, including pressures, temperatures and any driver, track or other names in those fields. Anyone holding a valid share link can read it without a TPP account.
New account shares expire after 24 hours and can be revoked. Expiry stops access; it does not mean all stored copies are immediately deleted. Older links use the legacy sharing service and follow different access rules. Nothing is uploaded unless you choose to share.
7. Accounts, migration and messages
Create an account with your email and password, then verify your email with a one-time code. The authentication provider handles passwords and verification and recovery codes. We keep your account identifier, verified email, access and expiry records, terms acceptance and marketing preference. A session record enforces one active desktop session per person. Protected local credentials allow access offline for up to 30 days, limited by licence expiry.
Migration verifies ownership of the existing licence and its associated email and preserves the original expiry. Current account licensing is not bound to a hardware identifier.
Product-news email is optional. You can withdraw that choice in your profile. Verification, recovery and other service messages are separate. Internal Sales notifications support account and licence administration; they do not turn a declined marketing choice into consent.
If you choose to send feedback, the message includes your text and category, account email and identifier, app version, operating system and current screen. A screenshot is attached only if you choose to include it.
When you use a referral code, we record the code, referring and referred accounts, verified registration, qualifying annual purchases and the credits earned or redeemed. These records administer discounts and prevent duplicate or self-referral claims. Your referral balance does not reveal other users’ email addresses. Authorised staff can inspect individual records in the internal dashboard. Suite-credit use links the relevant product and redemption records.
8. Why, and on what legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Providing account access, licence migration, renewals and requested referral rewards | Account identity, verification, licence and referral records | Performance of a contract |
| Finding and fixing faults — above all installations where the app fails to start | Failure reasons, app version, operating system, counters | Legitimate interest in a working product |
| Understanding which features are used, to decide what to build and what to drop | Feature counters, pair and circuit counts, activity days and hours | Legitimate interest in improving the product |
| Showing a session on your phone | The runs of the session you chose to share | A service you explicitly requested |
| Optional product-news email | Email and marketing preference | Consent, withdrawable at any time |
9. Who else is involved
Supabase supplies authentication and the database for accounts, licences, preferences, usage, referral records and shared sessions. Cloudflare supplies the website, account API, bot protection, service email, internal dashboard and new update distribution. GitHub distributes existing public releases and bridge installers.
Authorised MotorsportSoftware staff access records for service administration, support and the purposes above. We do not sell usage reports. Providers may operate in multiple countries; a database hosted in the European Union does not mean every service operation stays there.
10. How long it is kept
Account information and consent history are retained for the life of the account. Licence and purchase records are kept for the licence term and any required accounting period. Referral records support outstanding credits, redemptions and abuse checks. Weekly usage is kept while useful for product assessment; contact support for deletion or an objection.
Feedback, email-delivery and security records are kept according to support, security and service-administration needs and provider retention. The offline access window is not a server-data retention period. Local data, backups and exported files remain under your control until you delete them.
11. Your rights
You can ask what is held about you, ask for a copy, ask for corrections, ask for deletion, and object to processing based on legitimate interest — including the usage reporting described in section 3. Write to [email protected] from the address your account or licence is registered to, and you will get an answer.
If you are in the European Union and believe the processing is unlawful, you also have the right to lodge a complaint with your national supervisory authority.
12. Changes
When what the app reports changes, this page is updated and the date at the top changes with it. The account release described here is 3.0.0; the Help tab inside the app carries a short summary and a link back to this page.