Privacy and consent

The tracker sets no cookies, stores nothing on the visitor's device, never keeps a raw IP address, and counts visitors with a keyed hash that expires at UTC midnight and differs on every site. These are design properties of the software, not policies; the full construction, with every exception named, is in the Privacy Policy.

• Global Privacy Control: a visitor sending GPC is not measured. Honoured in the browser and again at our servers, so no snippet configuration can override it.
• Do Not Track: honoured by default; a per-site setting on the snippet.
• One consequence worth knowing: privacy-signal visitors are simply absent from your numbers, which is one reason totals can sit below cookie-based tools.

Most sites need no banner for this tracker, because nothing is stored on the device and nothing personal is collected. If your legal position wants explicit consent anyway, two pieces:

<script
  async
  src="https://c.getopen.so/oa.js"
  data-key="YOUR_TRACKING_KEY"
  data-collector="https://c.getopen.so"
  data-require-consent="true"
></script>

// when the visitor decides:
oa.consent("granted"); // or
oa.consent("denied");

• With data-require-consent, nothing is collected until granted.
• Denied is final for that visitor regardless of any other setting, and the choice persists in localStorage on their device.
• Every signal the script could send passes through one decision point; there is no path around it.

All analytics data is stored and processed in the European Union (Helsinki, Finland) and does not leave that infrastructure. Country and city come from a database file on our own servers; no IP address is ever sent to a geolocation service. The full subprocessor list is in the Privacy Policy.