Privacy
What leaves your customer's site.
The beacon runs in the browser of visitors who have never heard of us. The unit measured is one hour of one site, never a person.
Exactly what one payload contains
One row is one hour, of one site, on one version of your widget. A thousand visitors and a single visitor produce the same row, differing only in a counter.
Sent
- The customer site's origin — scheme and host, nothing else.
- The page path: query string dropped, segments shaped like an identifier replaced with « :id », truncated to 120 characters.
- Your widget version, as you deployed it.
- The hour, hour-aligned — never the minute, never the second.
- Integer counters: loads, renders, errors, blocks.
- A p95 of render time for that hour.
- The text of an exception your widget threw, every URL inside it reduced to its origin plus a redacted path.
Never sent
- No cookie, and no write to browser storage.
- No visitor identifier: no account, no device, no fingerprint, no random token.
- No IP address, no User-Agent, no referrer, no geolocation — there is no column to store them in.
- No query string: it is dropped, not truncated, because that is where session tokens live.
- No page content, and nothing a visitor typed.
How long it is kept
The history window is what the plan buys, and it is the same number that drives the server-side sweep.
- Watch
- 30 days of history
- Fleet
- 90 days of history
- Atlas
- 13 months of history
The inventory of discovered domains does not expire: it is the list of your customers, not telemetry. The sweep only removes observations and ingest errors.
Data protection officer
The decision is written down and reasoned, not defaulted into: GDPR Art. 37(1)(b) turns on regular and systematic monitoring of data subjects, and a row that resolves to nobody names none.
- Not a public authority — Art. 37(1)(a) does not apply.
- No special-category data and nothing about criminal convictions — Art. 37(1)(c) does not apply.
- Two residual exposures are written down rather than buried: an exception's free text, which only your code fills, and the visitor IP that any web server's access log contains.
- Six events reverse this decision, starting with the introduction of any visitor identifier at all. The day one of them happens, this page changes.
Data controller
A privacy policy has to name its data controller and the competent supervisory authority. Those fields are not filled in yet, and they are shown as such rather than hidden.
- Data controller
- Not published
- Postal address
- Not published
- Exercising your rights
- Not published
- Supervisory authority
- Not published
- DPO contact
- Not published