Skip to content

Data location

Stored and processed in the United States.

All customer data is stored in one region in the United States, and every visitor request is processed there, including requests from the EU, EEA, UK and Switzerland. The IP address and user agent are used in memory while the request is handled, then dropped. They are never stored.

Storage

United States

Databases, exports, queues and email all run in the United States. Database backups are made by our managed database service.

Every visitor, wherever they are

Processed in the US, in memory

Requests go to our US region over HTTPS. The IP address and user agent are used in memory for bot checks and the daily visit key, then dropped when the request is done.

What is stored

Minimized events only

Pages, sources, country and device categories, and a random visit ID that lasts one day at most. No IP address, raw user agent or persistent identifier is stored anywhere.

What is transferred, and for how long

Requests from visitors in the EU, EEA, UK and Switzerland are transferred to the United States. The personal part of each request, the IP address and user agent, exists there only in memory for the time it takes to handle the request. It is never written to a database, log, queue or cache. What is stored is minimized and identifies no one.

Transfer safeguards

  • Standard Contractual Clauses (2021/914, module 2, controller to processor) in our DPA, with the UK Addendum and the Swiss amendments for the Swiss FADP.

Infrastructure providers

Hosting, the content delivery network for the tracker script and every other provider that touches customer data are listed with their locations on our subprocessors page, with 30 days’ notice of changes.

Region-ready

Every workspace records its region, and nothing in our code assumes a single one. When demand justifies it, we can add an EU region without rebuilding the product.

How a request is handled

  1. Step 1 · Anywhere
    Visitor’s browser
    • Page URL and referrer
    • UTM parameters
    • Screen width and language
    • Your custom event properties
    • No cookies or local storage
    • No fingerprinting APIs
    • No third-party requests
  2. Step 2 · United States
    Ingest, 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
  3. Step 3 · Queued in the US region
    Minimized event
    • The minimized event only
    • No IP address
    • No raw user agent
    • No visit key or salt
  4. Step 4 · United States
    Storage 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

Common questions

Do you offer EU hosting?

Not yet. We launched with one storage region in the US and keep the product ready to add an EU region. Join the waitlist below: every signup counts toward the decision.

Is Privatus Analytics GDPR compliant if data is stored in the US?

We designed it so you can use it in line with the GDPR: IP addresses and user agents are used in memory only and never stored, nothing persistent identifies anyone, and transfers are covered by SCCs. Compliance also depends on how you use it. See the GDPR page.

Is any personal data stored for EU visitors?

The IP address and full user agent are never stored. They are processed in the US in memory only, then dropped. The minimized event can still contain what your pages put in URLs, so the PII scrubber removes emails and similar values, and the Acceptable Use Policy forbids sending personal data.

Join the EU hosting waitlist

Need your data stored in the EU? Leave your email and we’ll write once, when an EU region is available. We use this list only for that.