Aggregates

Every number in the dashboard is a running total. No individual hit record exists anywhere in the system. The counts in the board cannot be reversed into a list of events or visitors.

What an aggregate is

An aggregate is one number that represents many events. The visit count for a given day is a single integer. It was produced by adding one for each page load that occurred. Once the integer exists, the information about individual loads that contributed to it is gone. You cannot subtract one and ask which load it came from. You cannot sort the contributions by time. You cannot ask which ones came from mobile.

The per-dimension counters work the same way. The count of visits in the Fast speed band is one integer. The count of visits sourced from google.com is one integer. Each of those integers accumulated from many loads, and only the total is stored.

Why this system has no hit log

Many analytics systems store a row per visit and compute aggregates at query time. That design is flexible — you can filter, group, and re-analyze the raw data in many ways. It also means the detail data is sitting on a server, waiting to be queried or leaked.

StatelessID writes the aggregate directly. There is no prior step that creates a detail row. The incoming beacon is decoded, the correct counters are incremented, and the beacon data is not written anywhere else. A person who gains read access to the data store reads integers, not a log of events.

What you can and cannot do with the data

You can read totals by day, page path, source host, screen-size class, and speed band. You can set a date range and see how totals changed across it. You can compare pages by visit count. All of that is addition across buckets, which the stored integers support.

You cannot replay the sequence of visits. You cannot find the visit that came from a specific referrer on a specific day and ask what page it loaded. You cannot produce a list of sessions, or a list of page sequences for a visitor. Those operations require a detail table that does not exist in this system.

Data requests and regulatory obligations

If you receive a subject access request under a data protection regulation — from someone who used your site while StatelessID was active — you have no individually identifying record to provide or delete. The counts exist. The presence of any specific person in those counts cannot be isolated, because the counts do not contain person-level fields.

This does not mean StatelessID removes all of your obligations. What other data you collect about that person through your own systems still applies. StatelessID's contribution to your data picture is aggregate page load counts — counts that cannot be traced to individuals.

Troubleshooting

If you are comparing StatelessID visit counts to another tool and the numbers differ significantly, the definitions differ. StatelessID counts one beacon per page load with no deduplication, no bot filtering, and no session window. Other tools may deduplicate by cookie, filter known bots, or count sessions rather than loads. None of those adjustments apply here. The numbers measure different things.

If a legal review asks you to produce raw event data from StatelessID, the accurate answer is that no such table exists. The aggregates are the only output. You can describe the aggregate schema — counts by day, path, source, screen class, and speed band — and confirm that no per-event or per-person record was ever written.