Legal
What we collect, why, and how you can control it.
Last updated: August 2, 2026
Kerbside (kerbside.racing) is a Formula 1 statistics site. We do not require an account or ask for your name, email address, or other directly identifying information. We use a small amount of browser storage and, if you consent, a randomly generated identifier for basic quiz analytics. This page explains what that identifier is, what else we store, and the choices and rights you have over all of it.
We don’t run Google Analytics, ad networks, or any third-party tracking pixel — there is no advertising on Kerbside and nothing to fund with it. We don’t use traditional third-party cookies. The identifier described below is stored in your browser’s localStorage rather than a cookie, but EU/UK law treats the two the same way for consent purposes, so we do too.
localStorage. Neither is ever sent to us.A randomly generated identifier that we receive and can associate with repeat visits is best described as pseudonymous data, not anonymous data — under GDPR, online identifiers like this can still count as personal data even without a name attached. We treat it that way: it’s covered by the consent and rights described below, and it is never combined with anything that could identify you by name.
Each play records a per-device, per-day flag (started / completed / help opened) against the identifier, which we use to compute participation and retention curves — e.g. roughly how many people who played yesterday come back today. It is never used to build an individual profile beyond that, and never shared with or sold to a third party.
The identifier itself rotates automatically every calendar year, but rotation is not the same as deletion: the daily flag rows recorded against an identifier are not automatically deleted, since deleting them would defeat the point of measuring return visits over time. We do not currently have a fixed deletion schedule for these rows. They contain no name, email, or other directly identifying field — only a device id, a date, and three booleans.
Our hosting and network providers (Google Cloud and Cloudflare) also generate standard technical logs for every request — e.g. IP address, user agent, requested URL, and timestamp — for operational and security purposes, under their own retention settings. We do not separately collect or query this data for analytics.
We rely on your consent to store and send the analytics identifier. You can withdraw that consent at any time via “Cookie preferences” in the footer — doing so stops any new identifier from being created or sent, though it does not retroactively delete rows already recorded (see “Your rights” below for how to request that).
The quiz streak and your cookie choice are stored on the basis that they’re necessary to provide the specific feature you’re using — showing your streak back to you, and remembering a choice you already made so we don’t ask again on every page.
Depending on your jurisdiction, you may have the right to access, correct, or erase data associated with your analytics identifier, restrict or object to its use, withdraw consent, and complain to a supervisory authority — in Sweden, Integritetsskyddsmyndigheten (IMY), though you are not limited to that authority if you’re elsewhere. Because we don’t know who you are, we’d generally need the identifier stored in your own browser to locate any associated rows — reach out via the feedback page and, if you still have it, include the value of the cookie-consent-v1/analytics keys from your browser’s local storage.
Accept or reject the analytics identifier from the cookie banner on first visit, or change your mind anytime with “Cookie preferences” in the footer of any page. You can also block or delete browser-side data at any time using your browser’s own settings — clearing your site data for kerbside.racing removes the streak, your cookie choice, and the locally stored identifier, though not rows already recorded on our server (see “Data retention” above).
Kerbside is operated as a hobby project; the fastest way to reach us about this policy is the feedback page. The only third parties that process data on our behalf are our infrastructure providers: Google Cloud (hosting, database, and server logs) and Cloudflare (DNS, CDN, and DDoS protection). We don’t use a separate analytics, email, or error-monitoring vendor.
Kerbside is intended for a general audience. We do not knowingly request names, contact details, or other directly identifying information from children.
If this policy changes, we’ll update it on this page and update the “Last updated” date above.