Cookie policy

Last updated 2026-09-03

waybook.io sets no cookies. It writes nothing to local storage or session storage, loads no third-party scripts, fonts, images, embeds or tracking pixels, and creates no identifier for you. That is why there is no consent banner on this site: there is nothing to ask you about.

This is unusual enough to be worth substantiating, so the rest of this page says exactly what the site does instead.

What runs in your browser

Two small scripts, both written by us and served from this domain:

ScriptWhat it doesWhat it stores
Header stateWatches the scroll position so the header gains a background once you scroll past the top.Nothing.
Signup formValidates the early-access form, submits it without reloading the page, and reports the result. Sends three aggregate counts (see below).Nothing.

Both are inline in the page. There is no analytics library, no tag manager, no A/B testing tool, no session recorder, no chat widget and no advertising code. The typeface is served from this domain rather than from a font CDN.

What we measure

We count how often pages are viewed and how often the signup form is seen, started and completed. A count is sent as an event name and a page path — for example signup_started and / — and added to a running daily total.

What this deliberately does not include:

  • no cookie or device identifier of any kind, and nothing written to your device;
  • no email address, and no personal information — an event is never linked to a signup;
  • no query strings, and no personal data in any URL;
  • no cross-site tracking, because there is nothing to track with and no third party to track for.

The result is a table of numbers per day. It cannot be filtered down to a person, including by us, because nothing distinguishing was ever recorded.

Server logs

Delivering a web page requires your IP address, so our infrastructure provider processes one, and uses it to serve the page and to protect the site from attack. We do not store raw IP addresses in our own database.

Signup rate limiting is the one place we derive anything from an address, and it uses a short-lived one-way hash held for around 24 hours so the same source cannot submit the form hundreds of times. The address itself is not stored, and the hash cannot be turned back into one.

Email

Our emails contain no tracking pixels. We do not measure whether you opened a message or which links you clicked. Our email delivery provider records technical delivery information — whether a message was accepted, bounced or reported as spam — which we need in order to keep sending mail at all.

The application

The Waybook application itself uses local storage on your own device to keep your workbook available offline, and storage for the token that keeps you signed in. Both are strictly necessary for it to work, and neither is used for analytics or advertising. Sign-in is handled by Google’s identity service, which sets its own storage in order to keep you signed in; that is described in the privacy policy. Beyond sign-in, the application loads no third-party code.

If this changes

If we ever add something that stores information on your device for a non-essential purpose, we will add a consent mechanism before it loads — with accepting and rejecting equally easy — and update this page and the privacy policy first. We have no plan to.

Questions: privacy@waybook.io.