Know your traffic. Keep nothing about your visitors.

Cookieless web analytics: no cookies, no personal data, no IP addresses stored. There is no banner to show and nothing to leak.

That dashboard is this website's own traffic, measured by the thing you are reading about, and public because its owner chose to share it.

What "cookieless" actually means here

Nothing is stored on the device

No cookie, no local storage, no identifier of any kind. A visitor is recognised for one day by a hash the server computes and cannot reverse.

The day's key is thrown away

That hash is salted with a random value replaced every day, and yesterday's is deleted. The same person is a different number tomorrow, to us as much as to anyone else.

The address never gets further than the door

It is used to hash and to look up a country, then dropped by the first service that sees it. It reaches no queue, no log and no database.

One tag, 583 bytes

Put this in your <head>. There is nothing else to configure and nothing for your visitors to accept.

<script defer
  data-domain="your-site.com"
  src="https://wholestory.world/js/ws.js"></script>

583 bytes is the gzipped size of that script, and the build fails if it grows past a kilobyte. It counts pageviews, single-page navigations and any event you name.

Measured, not asserted

8,000

events a second accepted, with the service's own 99th percentile at 10 ms

983,780

events accepted in one run, and 983,780 rows stored — nothing was lost

4,279,247

records read a second time, changing none of the stored numbers

From a load test on one laptop running the production images, so it is a floor rather than a capacity — the generator ran out of room before the services did. The method, the full tables, and the two measurements that turned out to be measuring the measuring.