- Live telemetry
- Smart analysis
- Dynamic voiceover
- Auto director
Privacy
This website collects almost nothing: no cookies, no analytics, no tracking. The SimCast app does more, because it signs you in, counts your credits and sends your race to a server that writes the commentary. This page lists all of it — what we hold, where it goes and for how long — and says plainly where something is not automatic yet.
Last updated 18 October 2026
At a glance.
SimCast Ltd, a company registered in England and Wales. We are the data controller for the information described here. You can reach us at support@simcast.gg.
Just by visiting, nothing. These pages set no cookies, run no analytics, and store nothing on your device. Every file the page needs — images, fonts, the lot — is served from this site. Our hosting provider, Cloudflare, processes standard server logs (including IP addresses) to deliver the site and keep it up, as any web host does.
One exception: the home page has a video. Nothing is requested from YouTube until you press play. Then the player is loaded from YouTube’s privacy-enhanced address, and YouTube (Google) sees your visit as it would on any page you watch a video on. The links to youtube.com open YouTube itself.
The question box holds what you type: your email address, your name if you give it, what you race if you tell us, and the question itself. Alongside it we record the date, your IP address and your browser’s description of itself — not to profile you, but so that a form on an open website cannot be flooded by the same machine over and over. That is the whole record.
It is stored in a database on our own Cloudflare account, and a copy of what you typed (your name, email address, what you race and your question — not your IP address or browser) is emailed to our own inbox so we see it straight away. It is not sent to a form service, a mailing-list company, or anybody else.
If you email us instead, we hold whatever you send, the same way.
What we use it for. Answering you. That is all. There is no mailing list and you are not being added to one; we will not send you anything you did not ask for, and we will never sell, rent or share your details with anyone for their own marketing.
Our lawful basis. Legitimate interests: you contacted us about the product, so answering you is what you would reasonably expect.
How long we keep it. Until you tell us to delete it, or until it is clear the conversation has finished and there is nothing left to reply to. Nothing deletes these automatically yet; we go through them by hand.
Who else sees it. Nobody outside SimCast Ltd. Questions sit in a database on our own Cloudflare account, and each one is also emailed, by Cloudflare, to our Google (Gmail) mailbox. Mail to support@simcast.gg is passed on by Cloudflare’s email forwarding into the same mailbox.
You sign in to the SimCast app with Discord. We ask Discord only to identify you — we do not receive your email address, your friends or the content of any server. Discord’s access token is used once, at that moment, and thrown away.
What we hold about an account:
We may send you a direct message on Discord when your credits are running low or when credits are given to you.
What we use it for. To sign you in, run the AI booth, count credits, and keep the service secure and fair.
Our lawful basis. Contract — providing what you asked for — and legitimate interests, in keeping the service secure and preventing abuse.
How long we keep it. A sign-in session ends 180 days after you last used SimCast and is removed 30 days after that. The account itself, and the credit and usage records, are kept for as long as the account exists: they are the record of what was given and used. To have your account removed, email us (see Your rights).
Who else sees it. Cloudflare hosts the account server and its database for us. Discord is involved in signing you in, and our bot reads your role. When you broadcast, our booth server also receives your Discord ID, name and balance in the sign-in ticket, and records your Discord ID against each run (see below). Nobody else.
The SimCast app on your PC reads the race from iRacing. To write and speak the commentary it sends, to a SimCast booth server, a stream of the live session:
The booth server turns that into lines of commentary. To do so it sends text that names drivers (and may include iRating and licence class) to Anthropic, which writes the lines, and sends the lines to ElevenLabs, which turns them into speech that comes back to your PC. Those two companies keep what they receive under their own policies; we do not ask them to keep less.
Our server keeps a record of each run (your account, the track, the times, the league number) and a monthly usage record, and deletes them after 90 days; and a technical log that includes the text sent to the commentary writer — so it contains driver names — which is deleted after 30 days. It also keeps a copy of each broadcast’s requests to the commentary writer and the lines that came back, so that if you report a problem we can see what happened; that copy is deleted after 7 days. We use it only to look into problems, never to train anything. The commentary is written by an AI and can be wrong; if something said about you is wrong, tell us.
The track map is SimCast’s own: the app draws it from your own car’s position as you drive a clean lap. When it draws a map of a layout and you are signed in, it sends the map’s shape to our account server — 720 points round the lap, how big the shape is and how well the lap joined up, and nothing else (no time, car, lap time or telemetry) — so that everyone using SimCast gets a map of that layout; and the app downloads the map of a layout it has no lap of. We keep which account sent each map, so that a bad one can be taken down; if you ask us to erase your account, the map stays with no name on it.
You do not need a SimCast account to appear in a race that someone broadcasts with SimCast. Your name, iRacing ID, car, iRating and licence class are part of what iRacing publishes for the session, and they pass through the booth server as described above, and may be named in the commentary, the overlays and any clips. The broadcaster decides what they publish. If you want to know what we hold about you, or want it removed from our side, email us.
The Ask SimCast button in the Link app sends, when you press it: your question (up to 600 characters); the name of the tab you are on; the text the app is showing on its screens — headings, labels, buttons, balances and names, such as your Discord name (never anything you have typed into a box); a short line saying whether you are signed in, your balance and whether a broadcast is running; and, only if you leave the box ticked, the last part of the app’s log, with keys and tokens removed. The text and the log can contain your Discord name and driver names.
Our account server passes it to Anthropic to write the answer. No account ID or user ID goes with it, but your Discord name is in the text because the app shows it. We keep your question and the answer for 30 days, then delete them. The log and the screen text are used for that one answer and not kept by us.
Nothing leaves your PC until you have seen exactly what is in the report and pressed Send. A report can contain: what you typed; a short clip of the last minute on screen, with the commentary; the race’s replay file (which holds every driver in the session); the app’s log; and an analysis of that log. We remove keys, tokens, links that carry a signature, and your Windows user name from the text. We do not remove driver names.
Report files are stored privately on our Cloudflare account and deleted automatically after 7 days. The report’s entry — what you typed, the time, your account and the names of the files, which can include a driver’s name — stays. A notice goes to a private channel on our Discord with your display name, the product and version, the track, the lap and the first part of what you typed; never the files.
The older Report a bug button on the Help tab sends what you type, an email address if you give one, the last part of the app’s log and, if you tick the box, your settings with secrets removed. It is emailed to us, and may be copied to our private issue tracker and team chat.
If you switch it on, the app can upload your highlight reel — and, for league rounds, one clip per driver — so you can share a link. They are stored on our Cloudflare account and anyone who has the link can watch. A driver’s clip is named after the driver. They are deleted automatically after about a day; our record of the file names, which include the driver’s name, is not. The links are posted wherever you or your league chose: usually a Discord channel.
If your league connects a Discord channel to SimCast’s bot, the app can post that league’s results, standings and links there, naming the drivers. We keep which channel is connected and the name of the person who connected it, and, for 90 days, a log of each post (the link, the race and the time — not the words). Disconnecting stops posting; the record that it was connected stays. If you share your league’s season schedule through SimCast, your name is shown as the person who shared it to every broadcaster in that league.
The app’s log, your settings (including your sign-in token), your league files — including the race history with other drivers’ names and IDs — and any problem-report zips are kept on your PC. Your league files are also copied to the booth server for each broadcast, as described above. The log, your settings and the report zips are not sent unless you send them.
We do not sell your information and we do not use it for advertising. Several of these companies are based outside the UK, in particular in the USA; ask us if you want details of the safeguards each of them relies on.
Under UK data protection law you can ask us to:
Email support@simcast.gg and we will sort it out. There is nothing to pay and we will come back to you within a month. To delete an account we switch it off; delete its sign-in sessions, your helper questions, your problem reports and your clips (the files included); and remove your name and Discord ID from the account record and from anything else that carries them, such as a league schedule you shared. The credit and usage records are kept without your name, because they are the record of what was given and used, and the business has to keep its accounts. The booth server’s own records of your runs are deleted on their usual 90-day timetable, and the copy of your broadcasts’ commentary requests within 7 days.
If you are not happy with how we have handled it, you can complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113. We would rather you told us first so we can put it right.
If we change how any of this works we will update this page and change the date at the top.