Legal
Privacy policy
Last updated: 11 November 2026
This policy covers pacelaps.com, the status page at status.pacelaps.com and PaceLaps Race Control at app.pacelaps.com, including the PaceLaps agent. We keep as little as we can: race control works with car numbers, and drivers need no account.
Who is responsible
Christopher Monje, Merianstraße 5, 47506 Neukirchen-Vluyn, Deutschland. Email: support@pacelaps.com. More in the imprint.
This website
- No cookies, no tracking, no analytics. Your light or dark choice stays in your own browser.
- The website, the status page and the agent downloads are served by Cloudflare. Cloudflare processes your IP address and request data to deliver the pages and protect them from attacks (Art. 6(1)(f) GDPR, our interest in a working and safe site).
- The download page asks downloads.pacelaps.com for the newest agent version; that request also goes through Cloudflare.
- The status page at status.pacelaps.com shows whether Race Control works. Like this website, it sets no cookies and loads nothing from other sites.
Race Control
Stewards and league admins
- You sign in with Discord. We ask Discord only for your user id and display name, then end the connection; we never see your email or password. We also store a random pseudonym, your leagues and roles, and your settings (for example units).
- We need this to give you an account and run race control for your league (Art. 6(1)(b) GDPR).
Drivers
- Drivers join without an account. Your screen gets a random token, kept in a cookie and stored by us only as a scrambled value (a hash), together with your car number.
- Your league's roster holds driver names, iRacing customer ids, car numbers, teams and classes. The league's agent reads them from the iRacing session, or a league admin imports them. The league and we use them to run race control for the league (Art. 6(1)(f) GDPR, the league's and our interest in running its races).
- Drivers' screens and the audit log show car numbers, never names.
Race data
- Positions, laps, lap times, incidents, calls, penalties and results of a league's sessions, by car number.
- The audit log records each call and decision with the car numbers involved and the steward's pseudonym, never a name. It can't be changed afterwards.
The agent
- The agent reads the session from iRacing on the operator's PC and sends race data to Race Control. Its own logs stay on that PC.
- We store the agent's id and version, and keep the operator's iRacing name in memory while the agent is connected.
- Once a day the agent asks downloads.pacelaps.com for the newest version. It sends nothing about the operator or the league; like any download, Cloudflare sees the IP address. The operator can turn this off.
Issue reports
When a steward uses "Report an issue", we receive the note, the session's state and the steward's pseudonym. A copy goes to a private channel of ours on Discord and is deleted there with the report.
Cookies in Race Control
Race Control uses only cookies it needs to work: a session cookie and a security cookie while you're signed in, the driver screen's token (one year), and your theme choice (one year). No tracking or analytics cookies.
Server logs
Our servers log requests, including IP addresses, to keep the service running and safe (Art. 6(1)(f) GDPR).
Who processes data for us
- Hetzner Online GmbH, Germany: our servers, in Helsinki, Finland (EU).
- Cloudflare, Inc.: this website, DNS, the agent downloads and the storage for our backups. Backups are encrypted on our server before they leave it, so Cloudflare can't read them. Cloudflare may process data in the USA; it is certified under the EU–US Data Privacy Framework.
- Discord Inc.: the sign-in for stewards, our Discord server and the copies of issue reports, under Discord's own privacy policy.
- Microsoft Ireland Operations Limited: our support email.
We don't sell data or share it with anyone else, and we don't use it for advertising.
How long we keep it
| Data | Kept |
|---|---|
| Steward account (Discord id and name, settings) | While you use it. Deleted on request, or after 24 months without signing in or running the agent. |
| League content (settings, penalty catalog, procedures, sessions, calls, incidents, penalties, lap times, results) | As long as the league exists. Deleted with the league: by a league admin, or after 24 months without a session. |
| Audit log (car numbers, pseudonyms, agent ids; no names) | As long as the league exists. When a steward account is deleted, its entries no longer point to anyone. |
| Roster (driver names, iRacing customer ids, car numbers) | As long as the league exists. A driver’s name and customer id are removed on request; entries not seen in a session for 24 months are removed. |
| Driver screens (a random token, the car number) | Deleted 7 days after the driver switches car or league, or 90 days after the last use. |
| Agents (agent id, version) | Deleted after 12 months without contact. |
| Issue reports | 12 months. |
| Server logs (with IP addresses) | 14 days. |
| Backups | Daily copies for 30 days and monthly copies for 3 months. Deleted data is gone from them within about 3 months. |
| Support emails | 2 years after the last message. |
Your rights
You can ask us for a copy of your data, to correct it, to delete it, to limit its use, to receive it in a common format, and you can object to its use. Write tosupport@pacelaps.com; we answer within one month. Stewards can also download their data and delete their account themselves, on Race Control's Your leagues page. Drivers can ask for their name and customer id to be removed from every league's roster.
You can also complain to a data protection authority, for example the one for Nordrhein-Westfalen or the one where you live.
We make no automated decisions about you.
Changes
When this policy changes, we update it here and change the date at the top.