Privacy Policy — Rainline
This site is operated by the AI Agency. Last updated 1 August 2026.
What we collect
There is no account here: no sign-up, no email address and no profile, so we never ask you for anything that identifies you.
Like any website, our hosting records ordinary technical request logs (IP address, timestamp, the URL requested and your browser’s user-agent string) for security and diagnostics. We do not use them to build a profile of you. Advertising and analytics are covered in their own sections below.
What your browser sends us
Driving is entirely local: the car, the lap timing and the ghosts are all computed inside your browser, and none of that is streamed anywhere. While you are playing, your browser makes exactly two requests to us beyond fetching the page and its code. (A shared result link is a different page — it is described at the end of this section.)
When the page loads, it asks for today’s leaderboard. That request carries only today’s date — no identifier of any kind — and comes back with the ten fastest times of the day and a recording of the fastest run, so you have a ghost to race against.
When you beat your own best time, and only then, your browser sends us that run: the date, the total time, your best single lap, two numbers, and a recording of your inputs. The two numbers are positions in our own fixed list of adjectives and nouns — they are how a name like COBALT HERON is rebuilt at the other end. There is no text box anywhere in this game. You cannot type a name, and we never receive one. The recording is a list of how far the wheel was turned and whether the throttle and brake were held, sixty times a second; it describes a car, not a person.
We store one record per day, holding those ten times with their two numbers each, a count of how many runs were submitted, and the fastest run’s recording. It is deleted automatically 90 days later. There is no account to attach it to, no cookie identifying you, and nothing in it that could be traced back to you.
Three things stay on your device, in your browser’s local storage, and are never transmitted except as described above: your quality and audio settings; your personal best, with its time, the recording that lets the game replay it as a ghost, and the shape of the line you drove; and your chosen name as those same two numbers. Clearing your browsing data deletes all of it permanently, and because there is no account there is no copy anywhere for us to restore.
Opening a shared result link — an address beginning /r/ — is a separate page rather than the game, and it works differently. Everything it shows is encoded in the link itself, so opening one tells us nothing the address did not already carry, we store nothing when it is opened, and it asks for no leaderboard. It does fetch its result image from us, drawn fresh from that same link each time. Everything it loads comes from this site: it contacts no third party, so opening a shared link tells nobody but us that you opened it.
Advertising and cookies
We use Google AdSense to show ads. Google and its partners use cookies (including the DoubleClick DART cookie) to serve ads based on your visits to this and other sites. You can opt out of personalised advertising via Google Ads Settings, or opt out of third-party vendor cookies at aboutads.info/choices. Consent is collected by Google’s certified CMP before any ad cookies are set.
Analytics and your consent choices
We use Google Analytics 4 to count visits and see which pages get used, so Google receives that measurement as our analytics provider. It gets the pages you open, an approximate location worked out from your IP address, and your browser and device type. We send it no events of our own — not your lap times, not your settings, nothing from the game itself. Analytics runs only on our own live site: on a preview build or a developer’s machine the script is never loaded.
To do that, Google sets a first-party cookie named _ga in your browser. It holds a randomly generated client ID: not your name and not your address, but an identifier that lets Google tell one visitor apart from another and recognise the same browser when it comes back.
We want to be exact about the timing, because the two halves of the consent dialog are not treated the same here. Analytics storage is permitted by default, so the _ga cookie is set and measurement begins as the page loads — before you are shown the consent prompt, not after it. Advertising storage is denied by default: ad storage, ad user data and ad personalisation all start denied, so ad cookies genuinely do wait for Google’s certified consent platform. That platform then updates all four signals to match what you choose — but for analytics that update arrives after the cookie already exists, so if you decline there, clear it as described next.
If you would rather not be measured at all, you can block or clear the _ga cookie in your browser’s settings, use a tracker-blocking extension, or install Google’s Analytics opt-out add-on, which turns Google Analytics off on every site you visit. Nothing in the game depends on analytics: blocking it costs you no feature.
Your rights (GDPR / CCPA)
You can accept or reject cookies at any time, and you can clear them in your browser. We do not sell personal information.
Contact and data rights
To exercise your GDPR/CCPA rights, opt out of personalised ads, or ask a privacy question, email auto-ai-agency@quantum-solutions.hr. We respond to verified requests within 30 days.