Website analytics without cookies, IP addresses or a consent banner

• Page views and unique visitors per day, for the last 7 or 30 days.
• Average time on page, measured from the visit until the tab is hidden or closed.
• Top pages, top countries (from the network edge, not from the IP stored anywhere) and top external referrers.
• All of it on the same dashboard as errors and uptime — a drop in visitors next to a spike in errors tells a story a standalone analytics tool cannot.

Each request is reduced on the server to a hash of the day, a secret that rotates daily, the IP address and the browser signature. The hash is used to count a visitor once per day and is then meaningless: tomorrow’s secret is different, the IP is never stored, and the hash cannot be reversed. Nothing is written to the visitor’s browser — no cookie, no local storage, no fingerprint — so there is nothing to ask consent for, and the figures are not inflated by people who decline a banner.

Data is stored only as daily totals and breakdowns, never as individual visits. That keeps the volume bounded whatever your traffic and means there is no visit log to leak.

On WordPress, tick “Traffic analytics” in the plugin settings. On any other site, add one line before </body>, with your site’s reporting URL:

<script src="https://www.mysentry.co.uk/a.js"
  data-endpoint="https://www.mysentry.co.uk/api/ingest/<site>/<key>/collect"
  defer></script>

The script is under one kilobyte, uses navigator.sendBeacon so it never delays navigation, and is accepted only from the origins you allow in the panel. Details in the documentation.

This is not a replacement for a full analytics suite: there are no funnels, sessions, events or user journeys, by design — those require identifying people. It answers the questions a site owner asks most (is anyone visiting, from where, which pages, did the campaign land) with numbers you can publish without a privacy review.