Self-hosted analytics without cross-site tracking
Plausible Analytics keeps tracking at the site level instead of following people around the web. There are no cookies, no persistent identifiers, and no cross-site or cross-device tracking in the usual sense. Unique visitors are counted with a 24-hour session hash, which is enough for basic visitor counts without building a long-lived profile.
That model is a clean fit for self-hosted analytics where the point is site usage, not identity. It also narrows the amount of data held at rest. IP addresses are used briefly for approximate geolocation and then deleted, so the database does not keep a permanent copy for later inspection or mishandling.
What Plausible changes in the tracking model
Traditional website telemetry tends to collect more than it needs because the stack was built to identify repeat behaviour. Plausible is closer to aggregated website telemetry by design. It records page visits, referrers, engagement metrics, custom events, browser type, operating system, device category, and approximate country or region.
That is enough to answer ordinary operational questions. Which pages get used, which links bring people in, and which actions are worth tracking as events. It is not enough for a profile of an individual visitor across multiple sites, and that is the point.
Session hashes, no cookies, and no stored IP addresses
The session hash gives Plausible a way to count unique visitors over a short window without dropping a cookie onto the browser. The difference matters in practice because cookies travel with the user, while a short-lived hash does not become a durable identifier in the same way. Once the 24-hour window passes, the count resets.
Stored IP addresses are also off the table. Plausible uses them for location approximation, then deletes them. That leaves country or region level geography in the reports, which is useful enough for broad traffic patterns and dull enough to avoid pretending it knows more than it does.
Public dashboards as part of the setup, not a side effect
Public dashboards are part of the design, not an awkward extra. In the Open Home Foundation deployment, the same aggregated metrics shown internally are also exposed to visitors through public dashboards linked in site footers. That makes the telemetry visible rather than hidden behind an internal login that no outside reader can inspect.
That choice changes the trust model. Anyone can see what is being counted, which avoids the usual “trust us, it is anonymous” routine. It also forces the setup to stay at aggregate level, because a public dashboard full of personal detail would be a self-inflicted problem with a clear paper trail.
Where the privacy boundary still sits in daily operation
Privacy-first tracking still collects data. The gap is narrower, not empty. If you are running Plausible in a self-hosted stack, the daily boundary sits around what you count, what you expose, and what you let users switch off.
The Open Home Foundation setup disables journey tracking features and strips out affiliate links and other tracking elements. That keeps the analytics focused on page-level use and custom events rather than visitor path reconstruction. It is a sane boundary, but it is still a boundary that has to be held in configuration.
What still gets collected for aggregated website telemetry
Aggregated analytics is still telemetry. It tells you which pages were visited, where visits came from, which devices were used, and which custom events fired. That can include button clicks, downloads, and sign-ups, which is often enough to spot whether a page is doing its job or just sitting there looking busy.
There is a trade-off here. If you remove that visibility entirely, decisions get made on guesswork and the guesswork tends to be wrong in predictable ways. If you keep the telemetry, you need to accept that even privacy-first tracking still records behaviour in a way users may not expect if they only look at the page itself.
Why ad-blocker opt-out is a blunt but workable control
There is no consent banner for turning the analytics off. Opt-out depends on ad blocker rules that stop the Plausible script from loading. In the Open Home Foundation setup, that means a filter rule can block the script, while an allow rule can reverse it for someone who wants the dashboard to load.
That is a blunt control, and blunt controls have blunt edges. If an ad blocker does not already catch the Plausible script, analytics still runs. Users also do not get a tidy preference box for basic server-side usage information, which is the sort of thing that tends to annoy privacy-minded readers while remaining operationally simple for the site owner.
It is a workable arrangement because it matches the model: no cross-site tracking, no persistent identifiers, public aggregates, and a visible opt-out path through the browser layer. It is not a magic shield, just a narrower path through the mess.
