Privacy
What this site measures, and what it doesn’t
allowed.bike is a reference you read, not an account you keep. This page is written from the code that actually runs—what analytics sees, what the two forms send, and where it all goes—so you can check it against reality rather than trust a template.
01 / Analytics
Google Analytics, loaded lightly and told to forget the details
The one page that carries your bike’s specs never hands them to analytics—they are stripped off before Google sees anything.
The site loads Google Analytics 4, and only when a measurement ID is configured for the deployment. It loads after the page is interactive, so it never blocks the content you came for. IP addresses are anonymized. GA4 sets its own measurement cookies to count repeat visits; that is the extent of the tracking here.
- Only the bare path is recorded
- Before analytics fires, the page pins the URL it reports to
origin + pathname—the query string and the#hash are dropped. Google records that you viewed /check, never the specs after the?. - Why that matters here
- The checker encodes your bike’s specs in the query string so a verdict is shareable by link. Stripping the query before analytics runs is a deliberate choice: those specs stay between you and your browser, and never turn into an analytics event.
02 / The two forms
Corrections and rider experiences are stored for review
Two forms on the site accept a submission. Each one writes its contents to allowed.bike’s versioned content store so the people who run the site can review it. An email may also be sent as a courtesy ping, but email is not the stored record.
- The corrections form
- Stores the note you write about what looks wrong, plus the canonical source-page URL, state name and slug, and claim ID when available, while the statute or citation and a reply email remain optional. Corrections are private triage signals and are never published as rider reports.
- The rider-experiences form
- Stores the state and what happened, plus—each optional—the bike or class involved, an approximate date, a citation or ticket detail, and a reply email. Every experience is read by a person and moderated; nothing you send is published on the site without that review, and it is always kept separate from the cited law.
03 / What the site doesn’t do
No accounts, no advertising, no cross-site tracking
There is nothing to sign in to—the site has no accounts and no login. It runs no advertising and sets no ad or cross-site tracking cookies today. The only third-party the pages load is the Google Analytics measurement described above.
04 / Where it lives, and how to reach us
Form submissions live in the site’s private content store
Submissions live as versioned records in the private content store used by the site’s operators. A courtesy email may contain the same details. We make no automated-deletion promise the code doesn’t keep. Analytics data lives in Google Analytics under the operators’ account and Google’s own retention settings, not on this site.
Questions, or something here that doesn’t match what you see the site doing? The corrections form reaches us—there is no public email address to write to on purpose.