Privacy

What we collect, in plain words.

This page describes the analytics service. It is written to be read by the person deciding whether to install it.

What is stored for every event

Stored	Derived from
Page path	The URL, query string removed unless allow-listed
Referrer host	The referrer, path removed
Country	Connection, resolved at the edge and then discarded
Device class, OS, browser family	User-agent, bucketed — not the raw string
Visitor hash	IP + site key + daily salt, hashed at the edge
Event name and properties	Whatever you send

What is never stored

The IP address. It exists in memory at the edge long enough to be hashed, then is gone.
Cookies or any browser storage. The tag writes nothing to the device.
A cross-site or cross-day identifier. The salt rotates nightly, so yesterday's hash cannot be matched to today's and cannot be reversed.
Anything you did not send. We do not enrich, buy, or join third-party data.

Consent banners

Consent requirements in the EU are generally triggered by storing or reading information on the device, and by identifiers that persist. The tag does neither. That is why most customers run it without a banner.

We are not a law firm and this is not legal advice. The table above exists so your counsel can decide from facts rather than from marketing copy.

Where data lives

Frankfurt, Germany, with a warm replica in Helsinki, Finland. Backups stay in the same two regions. No sub-processor outside the EU touches event data.

Retention

Raw events are kept for your plan's retention window, then deleted, not archived. Aggregates older than the window survive as counts with no per-event detail.

Your requests

Because we hold no identifiers, we usually cannot locate "a person" in the data at all — which is the point. For account data (your email, billing records), write to privacy@slatecadence.com and we will export or delete it within 30 days.

Last updated 2 September 2026.