Legal
Privacy policy
The short version: both apps run on your own PC and keep your data there. The only thing Apex Labs holds is your free licence key, if you choose to get one. This website sets no cookies.
Last updated 18 November 2026
Who we are and what this covers
Apex Labs makes Windows tools for sim racing. This policy explains what data those tools handle and where it goes. It covers:
- Apex Overlays, the in-game overlay suite for iRacing and Le Mans Ultimate, including its desktop app, standalone server and VR layer.
- Apex Commentator, the iRacing broadcast toolkit, including its control panel, stream graphics and dual-commentary feature.
- The Apex Commentator live-timing page, the public spectator website a broadcaster can turn on.
- The Apex Labs website and our GitHub repositories, where the apps are downloaded and supported.
"Apex Labs", "we" and "us" mean Shamoy Samuel, who runs Apex Labs from the United Kingdom. Apex Labs is not yet a registered company, so Shamoy Samuel is the data controller for anything you send to Apex Labs. Where this policy says "the host", it means the person running Apex Commentator and sharing a live-timing page.
What each product handles
Neither app has analytics, advertising or automatic crash reporting. The only sign-up is an optional licence key, covered in Licence keys. Everything below is stored in files on your PC unless the table says otherwise.
| Data | Product | Where it is kept | Leaves your PC? |
|---|---|---|---|
| Live game telemetry (speed, inputs, fuel, positions, other drivers' names and car numbers in your session) | Both | Memory only, while the game runs | Only to the live-timing page or a co-commentator, if you turn those on |
| Settings, layouts, themes, leagues, teams, championships, driver rosters, nicknames and photos you add | Both | App data folder (Commentator: %APPDATA%; exports in Documents\Apex Commentator\Exports) | Only if you export and send a file yourself |
| Log files (errors, what the app is doing, crash locations) | Both | App data folder; Overlays keeps the current and previous run, capped at 8 MB | Only if you send them to us for support |
| iRacing Data API credentials (client ID, masked client secret, username, masked password) | Overlays, league import | App config file; secrets stored hashed as iRacing requires | Sent only to iRacing's sign-in service |
| Garage 61 personal access token, plus your car and track | Overlays, Garage 61 overlay | App config file | Sent only to Garage 61 |
| GitHub access token for updates | Commentator, optional | App settings | Sent only to GitHub |
| Text in league calendar images you import | Commentator | Read on your PC by Windows' own text recognition (or Tesseract) | No |
| Your camera and replay position | Commentator, dual commentary | Memory only | Sent to the co-commentator you give your access code to |
| Driver names, car numbers, teams, classes, positions, gaps, laps, sectors, tyres, track position, league logos | Commentator live-timing page | Memory only | Published to anyone with the page link, through Cloudflare |
| Your page tab and pinned drivers | Live-timing page (spectators) | The spectator's own browser storage | No |
The live-timing feed is built field by field and leaves out iRacing customer IDs, notes, file paths and anything about the host's PC. Spectators connect to Cloudflare, never directly to the host, so they cannot see the host's IP address.
The local web servers the apps run listen on your PC only (127.0.0.1) by default. Overlays has an opt-in LAN access setting for a second streaming PC, and Commentator's co-commentator server is protected by an access code.
How data is used, and on what basis
The apps use your data only to do what you ask of them on your PC: draw overlays, run the broadcast, import your league, show a reference lap or publish timing you chose to share. We do not sell data, profile you or use it for advertising.
Under UK data protection law (the UK GDPR and the Data Protection Act 2018), and the EU GDPR where it applies to you, the bases are:
- Running the features you turn on (contract or legitimate interests): telemetry, league import, Garage 61, update checks.
- Your choice to publish (legitimate interests of the host and the league): the live-timing page. The host decides whether to run it and which drivers' details appear, so for that data the host or their league is the controller, not Apex Labs. Hosts should tell their drivers the page exists.
- Support (legitimate interests): anything you send us, such as a log file, a GitHub issue or a Discord message, is used only to answer you and fix the problem.
Services the apps connect to
The apps contact these services directly from your PC. Each one sees your IP address and the request, under its own privacy policy. Apart from the Apex Labs key service, Apex Labs does not receive a copy.
| Service | Why | When |
|---|---|---|
| GitHub | Update checks and downloads; track map library; Layout Market listings; car, class and corner data from Lovely Sim Racing's public repositories | On start and every few hours (updates); when a track, car or the Market is first needed |
| iRacing | League import (Overlays); public track map images | Only when you import a league or a map is missing |
| Garage 61 | Your best laps, team leaderboard and reference lap telemetry for the current car and track | Only if you add a Garage 61 token |
| Cloudflare | Downloading cloudflared and carrying the public live-timing page; Cloudflare sees spectators' IP addresses | Only while a host runs live timing |
| Apex Labs key service (on Cloudflare) | Checking your licence key | Only after you add a key: when the app starts and about once a day |
| Microsoft WebView2 | The Overlays installer may download Microsoft's web runtime | Install time, if it is missing |
Layout Market. Sharing a layout opens a GitHub issue form under your own GitHub account. The layout and your GitHub username become public in the Apex Overlays repository and in the Market list. To remove one, close or edit the issue, or ask us and we will remove it.
GitHub issues and Discord. Anything you post in our GitHub repositories is public and governed by GitHub's terms. Messages on Discord are governed by Discord's terms. Please don't post log files that contain names or tokens you'd rather keep private in public; send them to us privately instead.
Licence keys
Every user can get one free Early Access key for both apps on the Get your key page. It is optional: the apps work without one during early access. If you get a key, Apex Labs holds the data below in its key service, which runs on Cloudflare Workers with the database stored in Western Europe.
| Data | Why |
|---|---|
| Your Discord user number and username | To know whose key it is and show it back to you when you sign in |
| Your key, its tier and any team or league codes you add | To give you the features that come with them |
| For each PC using the key: a random PC id the app makes, which app and version, and the dates of its first and last check | To show you your PCs, keep the limit of 5 PCs per key and let you remove one |
| A sign-in cookie on the key page (we store only a scrambled copy of it), and a 10-minute cookie while you sign in | To keep you signed in for up to 30 days, and to protect sign-in against forgery |
We don't collect your email address or password, and we don't store IP addresses. Cloudflare still sees your IP address to deliver each request. Sign-in is handled by Discord, which shares only your user number and username with us (the identify permission). Nothing is posted to your Discord account.
The basis is contract: we use this data to provide the key you asked for. We don't use it for marketing or share it with anyone. You can see your key and PCs, sign out, or delete your key and everything stored with it at any time on the key page. Keys that haven't been signed into or used by an app for 24 months are deleted automatically.
This website
This website sets no cookies and uses no advertising. It is hosted on GitHub Pages, which keeps standard server logs, including visitors' IP addresses, under GitHub's own policy.
To see how many people visit and which pages they read, we use Cloudflare Web Analytics. It sets no cookies, stores nothing in your browser and doesn't fingerprint you or follow you across sites. When a page loads, a small script sends Cloudflare the page address, the referring site, your browser and device type, your country (worked out from your IP address, which isn't stored) and how long the page took to load. We only see totals, never individual visitors. Cloudflare handles this under its privacy policy. The basis is our legitimate interest in knowing which pages are useful.
To show the latest versions and release notes, your browser asks GitHub's public API for each app's releases. That request goes from your browser straight to GitHub. The answer is kept in your browser's session storage until you close the tab, so the site doesn't ask again on every page. Fonts and images are served from this site, not from third parties.
Retention, security, children and transfers
Retention. Data on your PC stays until you delete it or uninstall the app; updates never touch your settings or league data. Live telemetry, the live-timing feed and the co-commentator feed are held in memory only and are gone when the app closes. Support messages are kept for up to 12 months after the issue is closed, then deleted. Licence key data is kept while you use the key, as described in Licence keys.
Security. Local servers listen on your PC only unless you turn on LAN access or a sharing feature. The live-timing page loads nothing from other sites, blocks framing and is never cached. iRacing secrets are stored hashed. Tokens are kept in plain config files on your PC, so protect your Windows account and don't share those files.
Children. The apps have no minimum age and don't collect personal data from users. Getting a licence key is optional and needs a Discord account, and Discord sets its own minimum age (13 in most countries). If you are under 13, please ask a parent or guardian before contacting us for support or sending us a log file. A host showing a junior driver's name on a live-timing page should have their or their parent's agreement.
International transfers. GitHub, Cloudflare, Discord, iRacing and Garage 61 may process requests outside your country, including in the United States, under their own safeguards.
Your rights, contact and changes
Because your data stays on your PC, you can see, change, export or delete it yourself: use the app's export, delete the item, or uninstall and remove the app data folder. Your licence key data can be seen and deleted on the key page. If you are a driver who appeared on someone's live-timing page, contact that host or league first, since they control it.
For anything we hold, such as a support message, you can ask us to access, correct or delete it, or object to how we use it, by messaging shamz2 on Discord. An Apex Labs email address is coming soon and will be added here. If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office (ICO), the UK regulator, or to the data protection authority where you live. This policy is governed by UK law.
We will post changes here with a new date at the top. If a future version adds anything that sends data to Apex Labs, such as crash reports or website analytics, we will update this policy before that version ships.