Last updated 13 September 2026
Privacy policy
This policy explains how RivalSplit processes personal data when you use the website and connect a watch.
Data controller
RivalSplit is the data controller.
Data we process
- Your name, email address and a stable account identifier from Google when you sign in.
- Your name, Google address, optional watch model and message when you request beta access.
- Feedback you submit, its category and the associated user account.
- Your role, account status, language choice and sign-in time.
- Events, reference athletes, selected rivals, split setups and drafts.
- Names and technical identifiers for watches you connect.
- Required session data, IP address, browser information and technical error events.
- Privacy-conscious usage statistics such as normalised page path, referring domain, device category and a daily rotating one-way hash. Raw IP addresses, search text, email and participant data are not stored in analytics.
- Public start-list and result data received from supported timing providers.
Why we use the data
We use the data to process beta applications, follow up feedback, sign you in, manage beta access, save your setups, send information to your watch, display live splits and protect the service from misuse. Processing is necessary to provide the service you request. Product improvement, security logging and troubleshooting are based on our legitimate interest in operating a secure and stable service.
Google sign-in
Google verifies your identity and shares your name, email address and account identifier. RivalSplit does not receive your Google password and does not request access to Drive, Calendar or other Google services. Google's processing is governed by Google's privacy policy.
Timing data and Garmin
Start lists and checkpoint times are retrieved from supported timing providers. When you connect a Garmin watch, a technical device key, the selected setup and required split times are exchanged. RivalSplit does not sell personal data or use it for advertising.
Cookies
We use necessary cookies for the sign-in session, secure Google sign-in, protection of the sign-in and beta forms, and language selection. Traffic analytics do not use cookies. No cookies are used for advertising or cross-site tracking.
Storage and deletion
Account information and setups are stored while the account is active or for as long as needed to provide the service. Beta applications and feedback are stored for as long as necessary to review or follow up the enquiry. Local sign-in lock data is deleted after 24 hours, technical error events after 90 days and traffic analytics after 180 days. You may request access, correction, deletion, restriction or data portability by contacting us.
Your rights
You may object to processing based on legitimate interests and lodge a complaint with the Norwegian Data Protection Authority. Some data may need to be retained when required by law or to document security incidents.
Changes
This policy may be updated when the service or its providers change. The date above shows the latest update.