Use cases Privacy FAQ Blog About Request beta access
The receipt

Check what this site does, right here in your browser.

A privacy company’s website should be able to itemize what it does in your browser. This page is that itemization: no cookies, no local storage, self-hosted fonts, one production-only analytics script, and one user-initiated payload. Then it shows you how to verify every line without taking our word for it.

The claims
  • No cookies. This site sets none. Not for analytics, not for preferences, not for anything.
  • No stored state. No localStorage, no sessionStorage, no personalization. The page you see is the page everyone sees.
  • Self-hosted everything. Fonts, styles, scripts, and images are all served from this site’s own assets. A font CDN is a tracking surface with better typography, so there isn’t one here.
  • One analytics script, production only. On jointhewheel.com and www.jointhewheel.com, and only there, a single Plausible script loads. It records pageviews and six named events (Beta Request Started, Beta Request Submitted, Beta Request Success, Beta Request Error, CTA Click, FAQ Open) with a short, bounded set of properties. Never your email, never anything you type. On any other hostname it never loads at all.
  • One user-initiated payload. The beta access request form: your email, an optional company-context survey, and a fixed source label, over HTTPS, to our signup API. Nothing is sent until you press submit.

What your browser can count right now

A small first-party script on this page reads your browser’s own accounting (request timing entries, cookies, storage) and draws the results below, locally. The script makes no network request; it is in assets/prove-it.js if you want to read it first.

Check it yourself

Five checks anyone can run

The inventory above is our code telling you what your browser did. If you’d rather not take our code’s word for it either (correct), run the same audit by hand. Open your browser’s developer tools: press F12, or right-click anywhere on this page and choose Inspect. No programming required; every step below says exactly what to click and what you should see.

Network: watch every request

Click the Network tab, then reload the page so it records from the first byte. Read the domain column of every row. Every request should go to this site’s own address: the page, the stylesheet, two scripts, the favicon, and a handful of self-hosted font files. On jointhewheel.com you’ll see one more: a script and a pageview beacon to plausible.io. That is the complete list. No pixels, no tag managers, no session recorders, no chat widgets.

Cookies: expect an empty panel

Open Application (Chrome/Edge) or Storage (Firefox), click Cookies, then this site. The panel should be empty. This check also catches HttpOnly cookies, which page scripts (including ours above) cannot see.

Storage: expect that empty too

Same panel: Local Storage and Session Storage, then this site. Both should be empty. This site keeps no state in your browser: no preferences, no visit history, no personalization flags.

The beta request payload: watch a submit

With the Network tab still open, submit the beta access form on the home page (a test address is fine). You’ll see a single HTTPS POST to api.jointhewheel.com carrying your email, a fixed source label, and any optional company-context fields you filled in. Click the request and read the payload yourself. Server-side it lands in one PostgreSQL table for beta-request contact, and the response is deliberately uniform: it never reveals whether an email is already on the list, so the form can’t be used to probe who signed up.

View source: read the whole thing

Right-click, View Page Source. This page and its two scripts (site.js and prove-it.js) are short, dependency-free, and written to be read. The analytics allowlist, the production-hostname gate, and the exact beta-request payload are all plainly visible in site.js. If a page ever does more than its source shows, that’s a bug report we want.

What this page cannot prove. A browser can show you what it sent and stored; it cannot show you a hosting provider’s request logs or what a server does after a request arrives. Those live on our side of the line. This page keeps the browser side of the story honest and checkable; the privacy policy covers the rest.

AI visits · it never ownsRequest beta access →