Reference
What we read — and what we never touch
We're a transparent proxy. Your visitors' data streams through us to your origin and back; our code reads only an explicit allowlist of advertising signals and passes everything else through byte-for-byte.
The boundary
This is an allowlist, not a blocklist — if it isn't on the list below, we don't read it. The same boundary is enforced in code and covered by automated tests on every release.
What we read
- Ad click IDs — fbclid, gclid, ttclid, msclkid and the like
- Campaign tags — utm_source / medium / campaign / content / term, plus ref and aff
- Our own cookies — your Hyper Tracking visitor ID and Meta’s _fbp / _fbc
- The page hostname and path — every other query parameter is stripped off first
- The User-Agent and Referer (with its own query string removed)
- Visitor country, and a one-way hash of the IP address — never the raw IP
What we never touch
- Passwords, and any login, account, or admin page
- Card numbers, CVVs, and other payment fields
- Tokens, API keys, secrets, and authorization headers
- Response bodies — what your site sends back is never read, stored, or logged
- Raw email addresses — on checkout pages the email is hashed at the edge, never kept in the clear
- Anything not on the read list — it passes straight through untouched
The one exception
If you enable our pixel, a single first-party analytics script is streamed into your page's <head> — the rest of the page is still never read. That's the only time we touch a response at all.
Where the full policy lives
The legal version of this page — retention, subprocessors, your rights — is in our Privacy Policy and subprocessor list.
Questions about a specific field or page on your site? support@hypertracking.io — we answer fast, and including your store's web address speeds things up.