Privacy
Cookieless web analytics that measures without tracking people
Every privacy claim we make has a technical explanation. This page describes exactly what happens to a pageview, what we store, what we never store, and how you can check it yourself.
Don’t take our word for it
These tools are run by other organizations. Each link scans this website fresh, so you see today’s result, not a screenshot we chose.
Mozilla’s scanner grades a site’s security headers, such as its content security policy, HTTPS enforcement and cookie settings.
Check it yourself (opens in a new tab)Blacklight visits a page like a real visitor and reports ad trackers, third-party cookies, fingerprinting, session recording and keystroke logging.
Run the scan (opens in a new tab)The data journey
Every visitor request, including requests from the EU, EEA, UK and Switzerland, is processed in our US region. The IP address and user agent are used in memory while the request is handled, and dropped before the minimized event is stored.
-
Step 1 · AnywhereVisitor’s browser
- Page URL and referrer
- UTM parameters
- Screen width and language
- Your custom event properties
- No cookies, and no local storage except a visitor's own opt-out choice
- No fingerprinting APIs
- No third-party requests
-
Step 2 · United StatesIngest, in memory
- Country from the Cloudflare header
- User agent → browser, OS, device
- Bot checks and your traffic rules
- In-memory visit key
- IP address dropped after the request
- Full user agent dropped after the request
- PII scrubbed, query strings trimmed
-
Step 3 · Queued in the US regionMinimized event
- The minimized event only
- No IP address
- No raw user agent
- No visit key or salt
-
Step 4 · United StatesStorage and dashboard
- Pages, sources, campaigns
- Country and device categories
- Random visit ID (one day at most)
- Event properties
- Nothing that identifies a person
- Nothing that links days, sites or devices
What we collect, and what we never collect
Collected (after minimization)
- Page. Hostname and path. Query strings removed except campaign parameters and your allowlist. Fragment removed unless you use hash routing.
- Referrer. Domain and path of the referring page. Query removed, internal referrers blanked.
- Campaign. UTM parameters and ref. Ad click IDs (gclid, msclkid, fbclid) are reduced to a yes/no flag.
- Location. Country only, from the country header our network provider (Cloudflare) adds to each request. No region, city or coordinates.
- Technology. Browser, operating system (family and major version), device type, screen size range, language.
- Engagement. Visible time on page and scroll depth in 10% bands.
- Time zone. The name of the browser’s time zone, such as America/Denver. A browser running on a server is rarely set to the time zone of the country its request comes from, so we compare the two to help tell bots from people. That happens in memory, then the time zone is dropped. It is never used as a location and never stored with a visit or an event. It is kept only in the bot training records of Advanced Bot Detection (honeypot hits, and samples from our own sites) for 12 months.
- Events. Names and up to 30 typed properties you choose to send, after PII scrubbing.
Never collected or stored
- IP addresses. Used in memory for bot checks and the daily visit key, then dropped. Never written to disk, logs, queues or databases, not even for bots.
- Full user agents. Parsed into categories in memory, then dropped.
- Cookies and device storage. No cookies, localStorage, sessionStorage or IndexedDB (except a visitor’s own opt-out choice).
- Fingerprints. No canvas, WebGL, font, audio or battery APIs, and no extra client hints.
- Persistent identifiers. Nothing that lasts beyond one day, or links sites or devices. No user profiles.
- Precise location. No coordinates.
- Third-party requests. The tracker talks only to Privatus Analytics.
PII scrubber. Before anything is stored, paths, referrers and event properties are checked for email addresses, long identifiers, token-like strings and long digit runs such as phone or card numbers. Matches are replaced with placeholders like [redacted-email], and each site sees how many redactions happened so leaks can be fixed at the source.
How visits are counted without cookies
- Each UTC day we generate a random 256-bit salt. It exists only in memory and is destroyed at the end of the day, plus a 30-minute grace period.
- For each hit we compute
HMAC(daily salt, site, IP, user agent)in memory and look it up in a memory-only store with a 30-minute inactivity timeout, capped at midnight UTC. - A new visit gets a random visit ID that is not derived from that key. Only the random ID is stored.
- When the salt is destroyed, nothing can link stored visits back to a device or to each other across days.
This is pseudonymous data: heavily minimized and not linkable beyond one day. We don’t describe it as anonymous.
Every field we store
Adding a stored field requires a written review of its purpose, minimization and retention. This is the current list.
| Field | Purpose | Minimization | Retention |
|---|---|---|---|
| Hostname, path | Pages | Query stripped except allowlist, PII scrubbed, path masks | Plan |
| Referrer host and path | Sources | www. and m. stripped, query dropped, internal blanked | Plan |
| UTM parameters, ref, paid click | Campaigns | Click IDs reduced to a yes/no flag | Plan |
| Country | Location | From the Cloudflare country header, IP dropped | Plan |
| Device, browser, OS (with major versions), screen range | Technology | Raw user agent dropped, screen bucketed | Plan |
| Visit ID | Visits | Random UUID, one UTC day at most | Plan |
| Event properties | Events | Up to 30 keys, typed, PII scrubbed | Plan |
| Time zone name | Training the bot score | Never stored with a visit or an event. Kept only with a honeypot hit or a sample from our own sites | 12 months |
| Filter counters | Bots, rules, redactions | Aggregates only, no IP | 13 months |
| Visit key (memory store) | Visit continuity | HMAC key, 30-minute timeout | One day at most |
| Daily salt (memory store) | Visit key | Never persisted | 1 day + 30 minutes |
“Plan” retention: 3 months on Free, unlimited while subscribed on paid plans, with per-site overrides.
Verify it yourself
- Open this page’s developer tools and go to the Application (or Storage) tab. You’ll find no cookies, and nothing in local storage from the tracker. The only thing the tracker ever stores is a visitor’s own opt-out choice. This site also keeps your light or dark theme there if you change it.
- Switch to the Network tab, filter by
/api/eventand reload. You’ll see one small request per pageview. - Open the request payload. It contains only the fields listed below: no identifiers, no fingerprint.
- Add
data-debug="true"to the script tag on your own site and watch the Console. Every hit is logged with the prefix[privatus], exactly as it would be sent, and nothing leaves the browser. A hit that is skipped logs the reason, and it works on localhost. See Test with nothing sent. - Read the tracker’s source. It’s MIT-licensed and short enough to read in one sitting. See open source.
Try the cookie and tracker scanner on your own site, too.
What a request contains
These examples show every field that can appear in each kind of hit. Most hits carry far fewer. The table below says when each field is sent.
{
"s": "pa_7Q2K9XH3AB",
"t": "pageview",
"u": "https://example.com/app?utm_source=newsletter#/pricing",
"l": "en-US",
"w": 1440,
"i": 0,
"r": "https://news.example.org/",
"h": 1,
"d": 1,
"g": 1,
"hp": 1,
"a": "webdriver",
"tz": "America/Denver",
"xp": "var_4M8T2KQ9ZD",
"p": { "plan": "pro" }
}
{
"s": "pa_7Q2K9XH3AB",
"t": "engagement",
"u": "https://example.com/app?utm_source=newsletter#/pricing",
"l": "en-US",
"w": 1440,
"i": 1,
"r": "https://news.example.org/",
"h": 1,
"d": 1,
"g": 1,
"hp": 1,
"a": "webdriver",
"tz": "America/Denver",
"e": 48210,
"sd": 80
}
{
"s": "pa_7Q2K9XH3AB",
"t": "event",
"u": "https://example.com/app?utm_source=newsletter#/pricing",
"l": "en-US",
"w": 1440,
"i": 1,
"r": "https://news.example.org/",
"h": 1,
"d": 1,
"g": 1,
"hp": 1,
"a": "webdriver",
"tz": "America/Denver",
"n": "signup",
"p": { "plan": "pro" }
}
| Field | Meaning | When it is sent | What happens to it on our side |
|---|---|---|---|
s | Site ID | Every hit | Used to find the site. Stored as the site the event belongs to. |
t | Hit type: pageview, engagement or event. The optional Web Vitals and click map modules add vital and click. | Every hit | Stored as the kind of event. |
u | Page URL, with non-campaign query parameters already removed in the browser | Every hit | Hostname and path are stored after path masks and the PII scrubber. Campaign parameters are stored, ad click IDs become a yes/no flag, and the rest of the query is dropped. |
l | Browser language | Every hit | Stored, cut at 16 characters. |
w | Screen width in pixels | Every hit | Stored only as a size range. Read in memory for the bot score. The exact width is dropped. |
i | 1 after the first real input on the page (pointer, key, touch or wheel), otherwise 0 | Every hit | Stored as a yes or no on the visit. Nothing about the input itself is sent. |
r | Referrer | Only when there is one | Host and path are stored after the PII scrubber. The query is dropped, and a referrer from your own site is blanked. |
h | 1 when hash routing is used | Only when the fragment is part of the page address | Used in memory to keep the fragment as part of the path. Not stored. |
d | 1 when the browser sends Do Not Track | Only when it is on | If the site honors Do Not Track (off by default), the hit is dropped and nothing is stored. Otherwise it is ignored. The flag is never stored. |
g | 1 when the browser sends Global Privacy Control | Only when it is on | If the site honors Global Privacy Control (on by default), the hit is dropped and nothing is stored. Otherwise it is ignored. The flag is never stored. |
hp | 1 on a page the site owner marked as a honeypot, 0 on a page marked as reached by people only | Only on pages marked for Advanced Bot Detection | A hit with 1 never becomes a visit or an event. It is counted as a bot and, on plans with Advanced Bot Detection, kept as a honeypot hit. A hit with 0 is counted as usual, and only our own sites keep a copy as a training sample. |
ch | 1 on a "confirm you're human" page that a site shows a random few visitors, people and bots alike | Only on pages marked data-hp="ch" | A hit with 1 never becomes a visit or an event and is not counted as a bot. On plans with Advanced Bot Detection it is kept next to the honeypot hits, marked as a challenge. |
a | Automation name: webdriver, phantom, nightmare or cypress | Only on a honeypot or challenge page, when an automated browser is detected | Kept with the honeypot hit. Ignored everywhere else. |
tz | Time zone name, such as America/Denver | Every hit, when the browser reports one | Compared in memory with the country of the request for the bot score, then dropped. Never stored with a visit or an event and never used as a location. Kept only with a honeypot hit or a training sample. |
xp | Experiment preview value, from pa_preview in the address | Pageviews only, when the address has pa_preview | Used in memory to show the previewed version. The pageview is not counted for the experiment. Not stored. |
p | Custom properties | Pageviews and custom events | Up to 30 are stored after the PII scrubber. Revenue and currency are stored as their own fields. |
e | Visible time on the page, in milliseconds | Engagement hits | Stored, capped at 4 hours. |
sd | Scroll depth, in percent | Engagement hits | Stored in 10% bands. |
n | Event name | Custom events | Stored, cut at 120 characters. |
v | Web Vital value | Vital hits (Web Vitals module) | Stored with the name of the vital, for a sample of hits. |
c | Short CSS selector of the clicked element, or the name the site gave it | Click hits (click map module) | Stored, cut at 512 characters. No coordinates or text. |
The optional survey module sends its own small requests. They are listed with the full reference in the docs. What a honeypot hit keeps is described in Advanced Bot Detection.
Where your data lives
US storage and processing, and transfer safeguards.
Compliance hub
GDPR, ePrivacy, US state laws and more.
Data Processing Agreement
Included in our terms.
Start measuring without cookies
No cookies, no fingerprinting and no consent banner needed for measurement.
Your first workspace starts with 14 days of Pro, free. After that it moves to the free plan, with 10k events a month, 3 sites and 3 months of history. No card required.