THE WHEEL

THIS SITE’S 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. Here is the current site’s receipt, with a live inventory and steps you can check yourself.

What the site code does

No cookies or stored preferences

The site’s own scripts do not set cookies or write to localStorage or sessionStorage. Form answers stay in the current page while you fill them in.

Assets served from this site, plus one analytics script

Fonts, styles, scripts, and images are hosted with the site. On jointhewheel.com, the site also loads Plausible, a cookieless analytics service, from plausible.io. It counts page views and a fixed set of events, such as a beta request being sent, and never receives what you type.

One request when you submit a form

The beta form sends your email address and any optional answers to our signup service at api-dev.jointhewheel.com, once, when you submit it. Nothing is sent while you type. The newsletter form sends your email address and a site source label to the same service when you submit. You must confirm the emailed link before receiving newsletter updates.

Actions you choose

Contact copy buttons write the selected address to your clipboard when clicked. Links to external sources take you to those services when you follow them.

LIVE BROWSER INVENTORY

What your browser can count right now

This check reads resource timing entries, accessible cookies, and storage counts locally. It sends no report. Read the inventory script →

This is evidence from this page, not a complete site audit. It cannot see HttpOnly cookies, hosting logs, all extension traffic, or what a server does with a request.

Five checks you can run yourself

  1. Watch the requests

    Open your browser’s developer tools and select Network. Reload the page, then inspect each request’s domain and initiator. Site assets should use this site’s address. Hosting services or browser extensions may add requests; inspect those separately.

  2. Inspect cookies

    In Application (Chrome or Edge) or Storage (Firefox), open Cookies and select this site. This also shows HttpOnly cookies that the inventory script cannot read. The site’s authored scripts do not set cookies.

  3. Inspect stored state

    In the same panel, check Local Storage and Session Storage for this site. The authored scripts do not write to either. Existing entries can come from earlier visits or other code on the same origin.

  4. Watch a beta request

    Open Network, then open the beta form, enter your email, and continue through the optional questions. Submitting sends one request to api-dev.jointhewheel.com. Select it to see exactly what it carries: your email address, the answers you picked, and nothing else.

  5. Read the source

    Use View Page Source to inspect the HTML and linked scripts. The beta flow is in signup.js; analytics and the signup address are in site.js; newsletter behavior is in newsletter.js. Compare the code with what you see in Network.