Privacy Policy

Effective 24 September 2026.

No account. No video hosting. A visit id so we can count people — not sell them.

When you open a page, this browser creates a random visit id and keeps it in local storage, not a cookie. After our counter accepts the visit, this browser also stores the first and last America/New_York calendar days it was counted.

That id is sent to our visit counter so we can tell a new visit from someone coming back on a later day. On the server we keep a short hash of the id — not the id itself — plus those days.

Anyone can read the public visit endpoint. It returns aggregate counts for the America/New_York day (unique and returning), a lifetime returner count, and a short note about how the counter works. It does not return your visit id or the hash.

We read the browser user-agent only to skip obvious bots from the count. We do not store it with the visit.

We do not sell personal data.

We do not run third-party analytics scripts, ad pixels, or tag managers on this site.

Today’s unique and returning counts cover the current America/New_York day. When the date changes, those two lists start over. We do not keep yesterday’s day-bucket as history.

The hashed id, with the first day and last day it was seen, stays so a later visit still counts as returning. There is no expiry timer. Each save keeps up to 50,000 hashed ids for first-seen and 50,000 for last-seen. Past that, further new hashes may not be saved. We keep these stats to measure returning visitors, and we will update this page if retention changes.

When a durable store is configured, those stats survive a deploy. Without one, they can live in memory for that server and reset.

Clearing site data in your browser drops the visit id on your device. The hash on our side can remain until it is no longer in the saved list.