Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) for the website fpvracemanager.com, the handbook and the FPV Race Manager app at racemanager.fpvooe.com is:
The full provider details are in the legal notice. For data protection requests, you can reach us at the contact details below.
Jakob WaldFerihumerstraße 464040 LinzAustriaIn short
The website uses no cookies, no analytics and no advertising. The app stores only what is needed for your account, race operations and – if you enable it – push notifications. There is no profiling, no advertising and no sale of data.
Scope and principles
This policy applies to all processing on fpvracemanager.com, in the handbook and in the app, including emails we send in connection with an account.
It does not apply to third-party websites we link to (e.g. fpvooe.com or social media platforms). The privacy policies of the respective providers apply there.
- Data minimisation: we collect only what is necessary for the respective purpose.
- Purpose limitation: race data is used for race operations and sports documentation, not for advertising.
- No advertising, no sale, no profiling and no automated decision-making with legal effect.
- Transmission is encrypted with TLS; passwords are stored only as hashes.
Legal bases
We process personal data only if there is a legal basis under Article 6 GDPR. In practice, these are:
- Article 6(1)(b) GDPR – contract or pre-contractual measures: account, profile, race registration, participation, results and support.
- Article 6(1)(f) GDPR – legitimate interests: secure operation, abuse prevention, server logs, sports documentation and public results, unless your interests override ours.
- Article 6(1)(a) GDPR – consent: push notifications. You can withdraw this consent at any time.
- Article 6(1)(c) GDPR – legal obligation: only where such an obligation exists in an individual case.
- The Austrian Data Protection Act (DSG) applies in addition.
We do not process special categories of personal data under Article 9 GDPR (e.g. health data). Please do not enter such data in your profile, race descriptions or free-text fields.
Hosting, server and logs
The app and the PostgreSQL database run on our own virtual private server (VPS) at Hostinger. According to our information, the server is located in Germany. Profile images are stored directly in the database; there is no separate image storage service.
The website is static. When you access the website or the app, technically necessary connection data is generated. The web server and the reverse proxy in front of it log in particular:
- IP address of the requesting device
- date and time of access
- requested URL, HTTP method and status code
- amount of data transferred
- referrer, if the browser sends one
- user agent (browser, operating system, device information)
These logs serve secure and stable operation, error analysis and defence against attacks (Article 6(1)(f) GDPR). We do not combine them with accounts and do not use them for advertising or profiling. Retention depends on the server log rotation and is as short as operationally possible.
Database backups are created daily and stored with access restrictions. An off-host backup via SFTP is possible; the transfer is encrypted over SSH.
Server logs
Individual requests are not stored permanently. We analyse logs only in the event of faults, security incidents or abuse.
Website and local storage
The website fpvracemanager.com is static. It uses no cookies, no analytics, no tracking pixels, no advertising networks and no social media plugins. Fonts are served locally; no Google Fonts requests are made. No videos or maps are embedded.
For language selection, the website stores a single entry in your browser localStorage:
- Key
- fpvrm-lang
- Value
- de or en
- Purpose
- Remembers your chosen language so the website does not redirect you again on your next visit.
- Location
- localStorage in your browser, not on our server.
- Deletion
- Can be deleted at any time in your browser settings; the entry does not expire automatically.
This storage is technically necessary for language selection and is therefore permitted without consent under Section 165(3) of the Austrian Telecommunications Act 2021 (TKG 2021); processing is based on Article 6(1)(f) GDPR. A cookie banner is therefore not required.
When you click an external link (e.g. fpvooe.com), you leave our offering. The privacy policy of the respective provider applies there.
No tracking
We do not count visitors, set advertising or analytics cookies, or create usage profiles.
Fonts
The website and the app serve their fonts themselves. Bebas Neue and Space Grotesk are local webfonts on our server; loading them establishes no connection to Google or any other font service.
Our emails also load no external fonts. They use system fonts that your email client already knows.
No font services
No fonts are loaded from Google or any other font service – not on the website, not in the app and not in emails.
Account and sign-in
You need a display name, an email address and a password for an account in the app. The email address must be verified. We store the following account data:
- display name
- email address
- password as a hash, never in plain text
- email verification status
- role (pilot, admin, super-admin)
- selected language (de or en)
- timestamps of creation, change and, if applicable, deletion
The app sets a session cookie for sign-in. It is httpOnly, Secure in production and SameSite=Lax, is valid for seven days and is extended on activity. On the server, we also store the IP address and user agent for the session in order to manage sessions and detect abuse.
To prevent abuse, we limit sign-ins, registrations, password resets and deletion requests. IP-based quotas are kept only in memory and not stored permanently. For the durable per-account quotas, we store no plain-text email addresses, but HMAC-SHA-256 digests with a timestamp and the respective purpose (e.g. login or recovery).
Admins can see an account display name, email address, verification status and role, as well as pilot profiles. Password hashes are not displayed.
Password
We cannot read your password. If you forget it, you can reset it via a link in an email.
Pilot profile
After registration, you create a pilot profile. A display name, profile image, video system and the receiving capabilities of your goggles are required for self-registration to a race. The Instagram handle is optional.
- display name (3 to 80 characters)
- Instagram handle (optional, format @name)
- video system: analog, HDZero, DJI, Walksnail or other
- video systems your goggles can receive
- profile image (optional; WebP, at most 512 × 512 pixels and 256 KB, stored in the database)
- timestamps of creation, change, retirement and anonymisation
Public visibility: at public races, your display name, Instagram handle (if provided), video system, receiving capabilities, profile image as a snapshot of your race entry, entries, placements, lap times and pilot history are visible to anyone who opens the race – even without an account. At private races, only participants and admins see this data.
The profile image itself can be retrieved through the profile API only by you and admins; public race views show the snapshot stored when you registered for the race.
Public means public
If you take part in a public race, your race data can also be seen by people without an account. At private races, visibility is limited to participants and admins.
Races, participation and results
For race operations, we store race metadata, the participant list and the race history. This includes in particular:
- race name, description, location, community, start time, track link, cup and visibility
- registration with a snapshot of name, Instagram handle, video system, goggle reception and profile image
- heat and channel assignments, spotter assignments and switches, ready marks
- lap times (at most three laps per heat), holeshot time and spotter rank proposals, including “no idea”
- start signal timestamps, results, placements, withdrawals and cup/overall standings
- audit and command logs: who triggered which change and when, with before/after state and hash values
- CSV exports of visible race data
This data is required for race operations, result calculation, traceability and sports documentation. Public races and their results are publicly visible; private races only to participants and admins.
We do not process special categories of personal data under Article 9 GDPR. Please do not enter health or other sensitive data in race descriptions, profile fields or free text.
Sports archive
Race and result data is retained long-term so that tables, cups and pilot history remain correct. When an account is deleted, it is anonymised.
Push notifications
Push notifications are voluntary. You can enable them per device in the app; the browser asks for permission. A verified account with a linked pilot profile is required. At most five devices per account are possible.
For push, we store:
- endpoint URL of your browser push service
- public encryption key (p256dh) and authentication secret (auth)
- user agent, expiration time, registration timestamps, last success and failed attempts
- hash of the revocation token and hash of the VAPID key used
- your category preferences: race start, next heat, now up, spotter call and registration open
- delivery rows with status, attempts, error codes and HTTP status
When sending, the message is handed to your browser or operating system push service (e.g. Google FCM, Apple, Mozilla or Microsoft). The payload is encrypted under Web Push; it contains a title, text and a link to the race, such as your pilot or heat name. We do not use push for advertising. Delivery rows are deleted after 30 days; event data has short lifetimes of 30 seconds to 24 hours.
The service worker stores on your device in IndexedDB (database fpvooe-push) the device binding with revocation token, recently seen event IDs and ordering metadata. This data does not leave your device and is pruned after seven days. The service worker creates no cache and no offline copy of the app.
The legal basis is your consent under Article 6(1)(a) GDPR. You can withdraw it at any time by signing the device out in the app, disabling notifications in your browser or deleting your account.
Withdrawal
The app works fully without push. You only miss notifications about start, heat and spotter calls.
Email delivery
We send emails through a Gmail account from Google (SMTP). This affects in particular:
- email address verification (link valid for 24 hours)
- password reset (link valid for one hour)
- notice that the password was changed
- account deletion confirmation (link valid for 30 minutes)
Recipient address, subject, content and technical delivery information are transmitted to Google. Google processes the data as a processor; a transfer to the United States is possible. The basis is the Standard Contractual Clauses or an applicable adequacy decision.
In our database, email content is encrypted (AES-256-GCM). After successful delivery or expiry, the content is deleted; the row with delivery metadata and an HMAC hash remains for at most 30 days. We send at most 200 emails per day and at most three per recipient per hour.
No marketing
We send no newsletters and no advertising emails. The emails serve only account, security and deletion purposes.
Recipients and processors
We disclose data only if it is necessary for operation, you have consented or a legal obligation exists. Recipients are:
- Hostinger – hosting of the server, database and backups, data centre in Germany
- Google – Gmail for email delivery
- your browser or operating system push services – only if you enable push
- an off-host backup target via SFTP designated by us – if configured
We do not sell data, do not disclose it for advertising purposes and do not create usage profiles. We conclude contracts with processors under Article 28 GDPR.
With Google, a transfer to third countries, in particular the United States, may take place. The basis is the European Commission Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework. Further information is in the Google privacy policy.
Retention periods
We delete data once the purpose no longer applies and no statutory retention obligation prevents deletion. The most important periods:
| Data | Retention |
|---|---|
| Account and profile | Until account deletion; race references are anonymised. |
| Sessions | Seven days; ends earlier on logout. |
| Verification, reset and deletion links | 24 hours, one hour or 30 minutes. |
| Email content | Deleted after delivery or expiry; delivery rows at most 30 days. |
| Push subscriptions | Until withdrawal or account deletion; delivery rows 30 days; device storage seven days. |
| Unreferenced profile images | Removed from the database after 24 hours. |
| Rate-limit digests | Pseudonymous HMAC digests with timestamps; no plain-text identity, no profiling. |
| Server logs | Short-term according to the server log rotation. |
| Backups | Seven daily and four weekly sets; older sets are overwritten. |
| Race and result data | Long-term for tables, cups and history; anonymised after account deletion. |
If a period does not mean anything to you, write to us; we will explain which data is still stored in your individual case and why.
Backups
Deleted or anonymised data may remain in backup sets for up to four weeks until those sets are overwritten on schedule. We restore individual records from backups only in the event of a specific operational or security incident.
Deleting an account and anonymisation
You can delete your account in the app. The process is deliberately two-step:
- 1You request deletion in the account settings.
- 2We send you a link by email; it is valid for 30 minutes.
- 3After confirmation, the account, password, sessions, push subscriptions and the link to the profile are removed.
Your profile is anonymised: name, Instagram handle, profile image and email address are deleted. Instead of your name, “Deleted account” with the deletion date is shown. The email address becomes available for a new registration.
Race and result data remains in anonymised form so that tables, cups and the history of other pilots are not distorted. Audit and command logs also remain with an opaque account ID; this ID contains no email address and no plain-text identity.
We do not physically delete the account row because races and logs reference it. Anonymisation is therefore the privacy-friendly implementation of deletion. If you instead request complete deletion, we will check whether legal or legitimate grounds prevent it.
What remains
Anonymised race results remain visible. Your name, image and contact details do not.
Your rights
You have the following rights under the GDPR:
- access (Article 15 GDPR)
- rectification (Article 16 GDPR)
- erasure (Article 17 GDPR), implemented through anonymisation
- restriction of processing (Article 18 GDPR)
- data portability (Article 20 GDPR)
- objection to processing based on legitimate interests (Article 21 GDPR)
- withdrawal of consent, in particular for push (Article 7(3) GDPR)
- complaint to a supervisory authority (Article 77 GDPR)
For access, rectification or erasure, an email to jakobfliegt@gmail.com is enough. We review your request and respond within one month; for complex requests, the period extends by up to two further months.
The competent supervisory authority is the Austrian Data Protection Authority, Barichgasse 40–42, 1030 Vienna.
Data security
We take technical and organisational measures to protect your data. These include TLS and HSTS for the connection, httpOnly/Secure/SameSite cookies, hashed passwords, role and access controls, rate limits, a Content Security Policy, encrypted email content and access-protected backups.
Server, database and backups are accessible only to a small group of operators. Credentials are not stored in the source code. Application logs are configured so that cookies, tokens, passwords and push keys do not appear in plain text.
Despite these measures, no transmission over the internet can be absolutely secure. If you suspect a security incident, write to us at jakobfliegt@gmail.com.
We report personal data breaches under Articles 33 and 34 GDPR to the supervisory authority and, where required, to you.
No tracking, no advertising
We use no analytics, no conversion tracking, no advertising networks, no social media plugins and no profiling. There are no custom audiences, no retargeting and no data sales.
There is no automated decision-making, including profiling, with legal effect. The app calculates heats, channels and results according to fixed rules; that is not a decision about you as a person.
The only optional data flows are push with your consent and email delivery through Google for account and security purposes.
Changes to this policy
We update this policy when processing changes. The current version carries the date at the top. For material changes, we inform you in the app or by email.
Please review the policy occasionally. If you do not agree with a change, you can delete your account or contact us.
Contact
For data protection questions, access requests or deletion requests, contact:
We usually respond within a few working days, at the latest within the statutory period.
Jakob WaldFerihumerstraße 464040 LinzAustria