Skip to content
DataVisitors

Count the visit. Follow no one home.

This page describes what the tracker and the pipeline actually do with a visit. The legal documents are linked at the bottom — and still marked as drafts.

What arrives

in memory only

ip
203.0.113.42
user-agent
Mozilla/5.0 (Macintosh; Intel Mac OS X…
url
/[email protected]&ref=nl
referrer
https://news.example/item?id=4821
cookie
— none set by the tracker

What is stored

sample record

country
TR — coarse location
browser
Chrome · macOS
path
/pricing
referrer
news.example
visitor
daily-salted hash, project-scoped

What the tracker does

Seven behaviours, each one enforced by the product.

A promise on a marketing page is only as good as the product that keeps it. Every row below is how DataVisitors behaves today, not a policy it hopes to follow.

  1. No cookie on a visitor

    The tracking script sets no cookie. It starts stateless.

  2. Nothing on the device where the law is strict

    In the EEA, the UK, Switzerland or an unresolved country nothing is stored on the device until your site's consent allows it; elsewhere local storage, unless you force Strict.

  3. A salt that expires every day

    A stateless visit is counted with the day's salt, minted once per UTC day.

  4. One person on two sites is two numbers

    The project is inside the hash, so visitors can't be joined across sites.

  5. Events go only to the host that served the tag

    The tag never beacons to a third party.

  6. A public link shows aggregates, never a visitor

    A share page can only read totals; it has no way to reach an individual visitor.

  7. Profiles stay closed until an administrator opens them

    People is off by default, and switching it on is recorded.

Your choice, per project

Three privacy regimes. Signals are honoured in all of them.

Global Privacy Control and Do Not Track are respected whichever regime a project uses; only an explicit consent from your own banner outranks them.

  • Default

    Automatic

    Stateless where the law is strict; device storage elsewhere when it is allowed. Cross-day analysis where permitted.

  • Most private

    Strict

    Nothing is stored on the device, anywhere, until your site's consent allows it. Until then every visit is counted with the daily salt only.

  • Relaxed

    Opt-out

    A first-party id may be kept on the device by default. Global Privacy Control, Do Not Track and the opt-out call are honoured, so visitors can say no and be respected.

Removal is never a paid feature

Export it. Erase it. Close the account.

Privacy exports, deletion and account closure are available on every plan. One erasure removes a person's events and their traits, each recorded in the audit trail; a finished erasure keeps a hash, never the key.

The legal text

Read the documents — and their status.

Accounts open by invitation

See your traffic honestly. Join the waitlist.

Join the waitlist Explore the demo

A site, an app, or a server · No cookies · Public links show totals