Back to RaceSki

RaceSki · Privacy

Updated 10 October 2026 · version 2026-10-10.1

RaceSki is currently being tested. Confirming that you have read this notice is not blanket consent.

Controller

Johan Hoel personally is the data controller. Contact: johanhoel94@gmail.com.

Data and visibility

When registering you enter your password twice to check that it matches. The confirmation is not stored. We store email, a salted password hash, login sessions, display name, height, weight, language, units, private power records, and the version and time of privacy acknowledgement. You may use a pseudonym. The selected class (women or men) is stored in your private profile and used automatically for race registration. Selection is optional in your profile but required for class-based races. It is also stored per event; later profile changes do not change historical results. Training draft level (1×–4×) is stored and affects drafting only at 2%. Race category is shown in separate public results and draft level in the training room and public summary. Body measurements are self-reported and used for virtual speed. Height and weight are private in the app. They appear only in your own profile and data export and are not sent to others in live data or results. We retain them internally to calculate speed in your events. They are personal data even when they are not automatically special-category data. Participants and spectators see display names, live watts, speed and position. The results archive is public without login: display name, distance, time and average watts. Height and weight are excluded from older results and API responses too. Previously public values may already have been copied by others. Interval averages are not published in the archive. Power records are shown only to you in the app; the administrator and service providers may have technical access. We cannot erase copies others make of public results.

Administrator access

The owner may grant accounts access to training, races or both. We store this permission on the account and link created events to the user ID. The owner finds the account using a user ID the user can share from their profile and sees the display name and assigned access. Other administrators can only create and delete their own events within their scope; these features do not grant access to other users’ email, account settings or private power records. The owner can delete all events and revoke access. Permissions are removed when revoked or the account is deleted; links to created events are cleared on account deletion. This processing supports secure administration under Article 6(1)(f).

Registration and role

Registration is stored separately from room presence. You can leave the room and select racer or spectator again. A racer who leaves stops and retains their accumulated distance. Switching roles does not erase participation or result data; account deletion removes them. Registrants who never start as racers are excluded from the results archive.

Purpose and legal basis

Account services, participation, virtual speed and training calculations deliver the service you request under GDPR Article 6(1)(b). Security, abuse prevention and the results archive rely on Article 6(1)(f). The archive serves the interest of documenting shared events. You may object by contacting us. New purposes requiring consent will have separate choices.

Retention and erasure

Accounts, records and results remain while the account exists. Delete your account in your profile with password confirmation: the account, sessions, records, participant data, messages and results are removed from the active database. Profile changes do not automatically update historical results. When you enter, a random technical power-session ID and last sequence number are stored to reject old or duplicate power messages. This is not a device ID. These values are internal, excluded from public responses and data exports, and removed on role change, completion of participation or account erasure. A quick reload can locate your open room through server presence and restore the same role without an additional browser room marker. This does not recover power or distance that never reached the server. Messages receive a temporary technical ID to prevent duplicate posts on retries. Chat is accessible only to users present in the room after the event ends, until everyone leaves or at most 30 minutes after the event ends. After 20 seconds without contact a user is considered disconnected. Access after leaving requires joining again; closed rooms cannot reopen. The app clears chat text from the screen when you leave. Cleanup currently runs on server requests; stored messages may remain longer if nobody uses the service. Expired sessions (90 days) and login limits (5 minutes) are also cleared. Password changes check the repeated new password on the server without storing the confirmation and end other sessions. Signing out or detecting an expired session clears private profile fields and chat from the view. Sign-out in another tab is detected on the same web origin; copies and screenshots outside the app cannot be erased. An independent scheduled cleanup job has not yet been activated.

Providers and backups

Hosting is through OpenAI Sites with Cloudflare Workers/D1. OpenAI Ireland Ltd is the processor under the ChatGPT Sites DPA. The agreement provides for standard contractual clauses or adequacy decisions for transfers outside the EEA. Actual storage location and log and backup retention periods remain unconfirmed. The platform also records traffic statistics, including visits and page views. Immediate erasure from backups and exclusively EEA processing cannot be guaranteed. Your browser stores a login token and language locally. An IP hash limits login attempts. Diagnostics can be enabled manually in your browser and show aggregate delays only, without names, watt values, messages or device IDs. Measurements are temporary, never sent to the server and cleared when diagnostics stop, you sign out or the page reloads.

Download your data

Your profile lets you download a JSON file containing your account, profile, private records, own participation data, retained own messages and login-session expiry times. Only your own authenticated session grants access. No public file is stored. Password hashes, salts, login tokens and other users’ participation data and messages are excluded. Keep the downloaded file private. The export covers the application database, not provider logs or backups. Contact us for other access requests.

Your rights

Contact us for access, correction, erasure and, where applicable, restriction, portability or objection. We normally respond within one month and explain any extension. You may complain to Datatilsynet or your competent supervisory authority.

ChatGPT Sites DPA · OpenAI sub-processors

johanhoel94@gmail.com