If We Are Breached

If the tracking store is read by an unauthorized party, they read arithmetic — page counts, source totals, speed distributions. There is no list of people, no email addresses, and no IP records tied to visit data.

What the tracking store contains

The tracking store holds visit counts organized by day, page path, source host, screen-size class, and speed band. These are integers grouped into classification buckets. No IP address is written into the tracking store. No user agent string is saved there. No name or email appears. The data that exists is arithmetic — counts per dimension value per site per day.

A person who gains read access to the tracking store sees numbers. They can tell that your site received N visits on a given day, that M of them came from google.com, and that K of them were classified as fast loads. They cannot tell who those visitors were, what they searched for, where they live, or what device model they used.

What the billing store contains

The billing store holds your site key, the hostname you registered, subscription cycle dates, and a reference handle for the subscription. No payment card number is stored by StatelessID. No bank account detail. Payment credentials live with the payment processor; the billing store holds a reference handle, not the secret.

The billing store holds subscription status, a one-way payer handle for rekey, access-key hashes, and domain hostnames — not operator email, name, phone, or visitor records. A breach of billing data does not expose who visited your site.

What cannot be reconstructed

An attacker with full read access to the tracking store cannot produce a list of people who visited your site. They cannot reconstruct session sequences. They cannot find out which pages a specific person visited in order. They cannot find out what someone searched for before arriving at your site. The data does not contain those records to reconstruct.

This is not because the data was anonymized after collection. It is because the data that was collected is aggregate counts, and aggregate counts do not encode the individual events that produced them. The structural choice that makes the system private by default is also what limits breach exposure.

Response and notification

If a breach is confirmed, StatelessID will notify affected operators. The notification will describe what categories of records were exposed. For the tracking store, that description is aggregate page load counts by dimension bucket. For the billing store, it would include subscription reference and access-key hashes — not operator email, name, or phone.

Your own regulatory obligations after a breach depend on what data was exposed and what laws apply to your site, your company, and your users. The fact that StatelessID's tracking store contains no personal data on your visitors is relevant to that analysis, but is not the complete answer. Consult your legal adviser with the specific facts of any incident.

Troubleshooting

If you are running a data protection impact assessment and need to document what StatelessID stores, the Features page on statelessid.com describes the tracking and billing stores. The tracking store schema — counts by day, path, source, screen class, and speed band — is described there accurately enough to document without needing server access.

If you have received a notification of a breach affecting StatelessID and need to understand what records were exposed, contact support with your registered domain name. We can confirm which stores were affected and whether your site's data was among the records accessed.