Your race.
Your data.

Local race operation

OpenSkiTime stores each event series in a portable local .ost database. It includes competitor details, race information, raw timing input, corrections and audit history. Preferences and online credentials are stored separately on the operator’s machine.

Registration, timing and result preparation work locally. Backups and exported files are under the operator’s control. Protect the race computer and decide who may access or receive those files.

Optional online features

Online features make requests to the services you select. FIS lookups and test submissions use FIS services; weather lookup uses Open-Meteo. Review the relevant service’s privacy terms before enabling them: FIS data protection and Open-Meteo terms.

Cloud live publishing

When the operator starts cloud publishing, the application sends a public competition snapshot and updates to the configured server. These can include competitor names, bib numbers, nation or club, classifications and results. Anyone with the viewer link can view that information; the link is not an access-control boundary.

The live service keeps published state in memory, with a maximum session lifetime of fourteen days. Restarting or scaling to zero discards that state. An active publisher can restore it. Session deletion removes the current view, but a browser may already have received a copy.

Deleted-session revocation markers are also in memory. A restart loses those markers; an independently retained, unexpired publisher credential can restore that session. Normal application deletion discards the credential. See the repository’s live timing guide for the full limitation.

The planned live.openskiti.me deployment runs in Azure Sweden Central. Persistent application-log storage is disabled by default. Application diagnostics must not include race payloads or credentials. Azure and network providers still process connection information such as IP addresses to operate their services.

The organizer is responsible for deciding which competitor information may be published, informing participants and handling requests about race data.

This website

This site uses no analytics scripts, advertising trackers, forms or application cookies. Its hosting and DNS providers process requests to deliver the pages. Following GitHub or other external links takes you to services with their own policies.

Support and reporting

GitHub issues are public. Use synthetic examples when reporting problems. Do not attach credentials, downloaded FIS lists or personal race databases.

For project questions, use the project’s GitHub page. Direct requests about a particular race’s personal data to its organizer.