Privacy Policy
Omni Regatta is a service for live tracking of sailing races, race replay and analysis. Race Recorder is the mobile app a participant uses to join an event and send their position. This document explains which personal data we process and on what terms, in line with Regulation (EU) 2016/679 (GDPR).
1. Who we are
The data controller is Sergei Gushchin, a sole trader operating as OMNI System Sergei Gushchin, ul. Kazimierza Porębskiego 13/29, 80-180 Gdańsk, Poland, tax ID (NIP) 5833439805, REGON 520401274 ("we").
Contact for privacy matters: support@osgps.pl or by post at the address above. We have not appointed a data protection officer.
2. When we are a controller and when a processor
- We are the controller of user account data, of data of participants who join an event themselves through Race Recorder or the website, and of the track and results archive we keep for analysis.
- The event organizer (a club, association or other body that creates an event) is a separate controller of the data it uses to run its regatta.
- We are a processor to the extent the organizer itself enters participant data into the service (for example entry lists or tracker assignments). The processing terms are set out in the Terms of Service.
3. Data we process, purposes and legal bases
| Data | Purpose | Legal basis |
|---|---|---|
| User account: email address, password (stored as a hash), organization name, role, date the Terms were accepted | Creating and running the account, sign-in, service emails (address confirmation, password reset) | Art. 6(1)(b) GDPR – performance of the contract for electronic services |
| Participant data: full name of the helm or sailor and of the crew (co-skipper, crew – optional), club (optional), boat name, sail number with country prefix, class, gender (optional), notes (optional) | Taking part in an event; display on the map, in results and in the race replay | Art. 6(1)(b) GDPR – providing the service to the participant; Art. 6(1)(f) GDPR where the organizer enters the data (legitimate interest: running and documenting the regatta) |
| Precise location while tracking is active: latitude, longitude, time, speed, course, accuracy, battery level; for hardware trackers also the device IMEI | Live tracking, start and finish timing, race replay, statistics | Art. 6(1)(b) GDPR; the app's access to location additionally requires permission in the phone's operating system |
| Track and results archive and derived data (manoeuvres, speeds, wind angles, comparisons) | A lasting regatta archive, and analysing manoeuvres, comparing races and producing recommendations for sailors – the core purpose of the service | Art. 6(1)(f) GDPR – legitimate interest in keeping a sporting archive and developing sailing analytics |
| Technical data: IP address, date and time of a request, browser or app type, server logs, raw tracker messages | Security, abuse prevention, troubleshooting | Art. 6(1)(f) GDPR – legitimate interest in keeping the service secure and available |
| Correspondence: email address and message content | Answering enquiries, handling requests and complaints | Art. 6(1)(f) GDPR; for complaints also Art. 6(1)(c) GDPR |
We do not process data for advertising, we do not sell it, and we do not use traffic analytics or cross-site or cross-app tracking. We do not make decisions based solely on automated processing that produce legal effects. Track analysis serves only the sporting assessment of a race.
Providing data is voluntary, but it is necessary to create an account or to take part in a tracked event.
An organizer can fill gaps in a boat's track with a GPX file, for example from the crew's plotter or watch. Points from the file are processed and shown in the same way as location from the app; the file itself is not kept.
4. What is publicly visible
If the organizer marks an event as public, any visitor can see the boat name, sail number, the full names of the helm and crew, the club, track, speed, course, times and results – live and in the archive. The organizer can switch off the display of names (together with the club) in the public view. Events not marked as public are visible only to members of the organizer's organization.
5. Location, background tracking and camera (Race Recorder)
Race Recorder uses precise location only after the participant starts tracking. Tracking may continue in the background – with the screen off or while another app is in use – so that the race track stays complete. The participant can stop tracking in the app at any time. Without a connection, positions are stored on the phone and sent once the connection returns.
Camera access is used only to scan event join QR codes. Race Recorder does not record video or photos.
6. Retention
- Tracks, results and event participant data – indefinitely, for as long as the service operates. A multi-year archive and the ability to compare races are the essence of the service. On request we delete or anonymise the data that identifies a person (name, notes); the track may then remain in the archive in a form that does not point to the person.
- Account data – until the account is deleted, and afterwards for the limitation period of any claims.
- Server logs – no longer than 12 months.
- Backups – no longer than 90 days from creation; data deleted from the service disappears from backups as that period passes.
- Correspondence – up to 3 years after the matter is closed.
7. Sharing
We use providers that process data on our behalf:
- Hetzner Online GmbH (Germany) – application and database server, located in Germany;
- Prociv Sp. z o.o., ul. Czerniawska 2A/27, 50-576 Wrocław, Poland, NIP 8971776931 (the vh.pl service) – email, including messages sent by the service.
Participant data is visible to the organizer of the event and, for public events, to all visitors (see section 4). Race Recorder is distributed through Google Play and the App Store, whose operators are separate controllers of download-related data.
Maps and weather data are fetched by your browser directly from external providers. They receive your IP address and technical request data, not account or participant data:
- Open Waters / VersaTiles and OpenSeaMap – nautical base maps;
- Esri (ArcGIS World Imagery, USA) – satellite base map, fetched when you select it;
- Open-Meteo – wind and weather data;
- OpenStreetMap Nominatim – place name for the event coordinates;
- EMODnet – bathymetry data;
- YouTube – only when the organizer has embedded a video with an event.
We do not sell personal data and we do not use participant data for third-party advertising.
8. Transfers outside the European Economic Area
Account, participant and track data is stored on servers in the European Union. Using the Esri satellite base map or an embedded YouTube video involves sending your IP address to a provider based in the USA. We do not transfer other data outside the EEA.
9. Your rights
You have the right to:
- access your data and receive a copy;
- have your data corrected;
- have your data deleted or its processing restricted;
- data portability for data we process under a contract;
- object to processing based on legitimate interest, including keeping your data in the archive;
- lodge a complaint with the Polish supervisory authority: Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa, Poland, or with the authority in your country.
Send requests to support@osgps.pl. We reply within one month. If your data was entered by an event organizer, you may also contact that organizer.
10. Cookies and browser storage
The website sets no cookies and uses no analytics or advertising tools. We use browser storage (localStorage and sessionStorage) only as far as needed to provide the service, which is why we do not ask for separate consent. We store:
- the sign-in token – to keep you signed in;
- interface settings – language, chosen base map, view and panel layout;
- the last opened event and your working context in the organizer panel;
- participant details entered in the join form – so you do not need to type them again.
You can remove this data by clearing site data in your browser settings; signing out removes the sign-in token. The providers listed in section 7 may use their own cookies if you use their resources (in particular embedded YouTube videos).
Race Recorder keeps the participant session (in the system's secure storage), the participant profile and the queue of unsent positions on the phone. This data is removed when you delete a saved event or uninstall the app.
11. Children
Minors take part in regattas too. The event organizer is responsible for obtaining a parent's or guardian's consent to a child's participation in a tracked event and to publication of the child's data. We recommend that organizers switch off the public display of names in events with children. A parent or guardian can request deletion of a child's data using the contact details in section 1.
12. Security
Connections to the service are encrypted (HTTPS), passwords are stored only as hashes, access to the server and database is restricted, and backups are made daily.
13. Changes
We may update this policy as the service evolves. The effective date at the top shows the current version. We will inform account holders of material changes by email or in the service.
Contact
OMNI System Sergei Gushchin, ul. Kazimierza Porębskiego 13/29, 80-180 Gdańsk, Poland
Privacy questions and data requests: support@osgps.pl