This Privacy Policy explains how League Race Director (“LRD”, “the Software”), published by Coy Media (“we”, “us”, “our”), handles information. It covers the LRD desktop application and the website at lrd.coymedia.us.
The short version
LRD has no servers and no user accounts. We do not collect your data.
LRD is a Windows desktop application. Everything it reads, computes, and saves stays on your own PC. There is no LRD backend, no analytics, no telemetry, no crash reporting, and no advertising. We cannot see your race data, your iRacing account, or anything you put on screen, because none of it is ever sent to us.
The only network connections LRD makes are the ones you ask it to make: to iRacing, using iRacing’s own official sign-in so LRD can show you your own data, and to any web address you choose to put in a URL overlay.
1. Information LRD stores on your computer
All of the following is written to your own disk and never transmitted to us.
Application settings and window layout — stored at %APPDATA%\League Race Director\window-config.json. Includes your overlay preferences, broadcast server settings, and your iRacing authorisation tokens (see section 2).
Licence token — stored at %APPDATA%\League Race Director\license.json. A signed token containing the name or organisation it was issued to, its tier, and its expiry. It is verified offline using a public key built into the app. No licence check ever contacts a server, so we receive no signal that you have installed or launched LRD.
Racer and broadcast profiles — overlay configurations, any logo or sponsor images you add, and the web addresses you enter for URL overlays, stored under %APPDATA%\League Race Director\.
Race Notebook — stored at Documents\LRD\Notebook\. Per-session race records: drivers seen in your sessions, lap and stint data, incidents, penalties, pit decisions, and any notes you write. This is your league’s data, saved in plain JSON so you can back it up, ZIP it, or delete it yourself at any time.
Diagnostic logs — written locally so you can attach them to a bug report. They are never uploaded automatically. If you choose to send us a log or a diagnostic export to help debug an issue, you are sharing it with us deliberately, and we use it only to investigate that issue and delete it once resolved.
2. Third-party connections you initiate
iRacing
If you connect your iRacing account, LRD uses iRacing’s official OAuth2 sign-in. You sign in on iRacing’s own site in your normal browser — LRD never sees or stores your iRacing password. iRacing returns access and refresh tokens, which LRD saves locally so you do not have to sign in every session.
With those tokens LRD requests, from members-ng.iracing.com, only the data needed for the features you are using: your member profile, your league and season information, track and car metadata, and session results. Car and track images are loaded from images-static.iracing.com. LRD also reads live telemetry directly from the iRacing simulator running on the same PC, through iRacing’s local shared-memory interface. None of this leaves your machine.
Your use of iRacing is governed by iRacing’s own terms and privacy policy.
URL overlays
LRD can render any web page you choose as an overlay. When you use that feature, LRD loads the address you supply, the same way a browser would. That means:
- The site you point it at receives whatever any web request carries, including your IP address, and can set its own cookies.
- LRD sends that site nothing about you — not your race data, your league, your iRacing account, or any other setting. It is a frame around a page you chose.
- Those pages run in a browser session kept separate from the rest of LRD, with no access to the application itself, and their cookies and storage stay walled off from anything else LRD does.
- The address you enter is saved locally in your profile so the overlay comes back next launch. Nothing about it is sent to us.
Point a URL overlay at anything and the ordinary rules of visiting that site apply, so use the same judgement you would opening a link in a browser.
If you point one at a Discord StreamKit widget to see your voice channel, that arrangement is between you and Discord: you authorise Discord’s own tool in your own browser, and LRD plays no part in it and never sees your Discord account.
Google Fonts
The LRD application window, and this website, load display fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). This means Google receives the standard request information — including your IP address — that any web font request involves. No LRD data or identifiers are included. If you prefer to avoid this, blocking those two hosts leaves LRD fully functional; the app falls back to fonts already installed on your system.
3. The broadcast server
LRD includes a local HTTP server (default port 7788) so streaming software such as OBS can load overlay pages, including from another PC on the same network. By default it binds to all network interfaces so a second machine can reach it.
It serves overlay pages, live session state, and images from your active broadcast profile. It is unauthenticated. Anyone who can reach that port on your network can view your overlay data. Do not expose it to the public internet, and do not port-forward it. You can change the port or turn the server off in Settings.
4. What we do not do
- We do not operate any server that receives LRD data.
- We do not use analytics, telemetry, usage tracking, crash reporting, or fingerprinting.
- We do not create accounts or profiles about you.
- We do not sell, rent, or share personal information — we do not hold any to share.
- We do not use your data to train machine-learning models.
- We do not serve advertising or embed third-party trackers in the application.
Because we hold no personal information about you, there is nothing for us to disclose in response to a data request, and nothing for a breach of our systems to expose.
5. Retention and deletion
You control all LRD data, because it lives on your PC.
- Disconnect iRacing — use the disconnect control in LRD’s iRacing settings to clear the stored tokens.
- Delete your race notebook — delete the
Documents\LRD\Notebook\folder. - Remove everything — uninstall LRD, then delete
%APPDATA%\League Race Director\andDocuments\LRD\.
If you have voluntarily sent us a log or diagnostic file, email us and we will delete it.
6. Children
LRD is not directed at children under 13, and we do not knowingly collect information from them. Because LRD collects nothing, there is no data for us to delete — but if you believe a child’s information has reached us through a bug report, contact us and we will remove it.
7. Your rights
Privacy laws such as the GDPR (EU/UK) and the CCPA (California) give you rights to access, correct, export, and delete personal information a company holds about you. Coy Media holds no personal information about LRD users, so there is nothing for us to produce or erase — your data is already entirely in your hands, in plain files you can read, copy, or delete. If you believe we hold something about you and want it removed, email us and we will act on it promptly.
For data held by iRacing, or by any site you load in a URL overlay, about your use of their services, contact them directly; those requests are outside our control.
8. International users
LRD processes data locally on your own device, wherever you are. Because no data is transferred to us, there is no international transfer of your data by us. Data you send to iRacing, or to a site you load in a URL overlay, is transferred and stored under their policies.
9. Changes to this policy
We may update this Privacy Policy. The “Last updated” date above will change, and material changes will be announced in the LRD release notes and the LRD Discord. If a future version of LRD ever begins collecting data, we will say so here and in the release notes before it ships.
10. Contact
Coy Media — League Race Director
Email: support@coymedia.us
Web: lrd.coymedia.us
Discord: discord.gg/4Gz8b3V9Pa
