Traffic numbers without a banner.

In the default mode the script sets no cookie and writes nothing to localStorage. A visitor is a server-side hash with a daily salt, so you get visitors, sources and pages without asking anyone for anything.

The problem. Sound familiar?

  • A consent banner added only so an analytics script may run.
  • Numbers that quietly lose every visitor who clicks Decline.
  • A tool that stores an id “because it is simpler”.

Where Tapll answers it.

  • 01

    Strict anonymous, the default

    No cookie, no localStorage. The IP address is truncated before it is stored and the query string is never collected.

  • 02

    Say what the number means

    Without an id a visitor is recognised for one UTC day, so a person returning on three days counts three times in a wider window. The panel says so next to the number.

  • 03

    Product analytics when you need it

    Retention and people across visits and devices, with `data-consent="banner"`: nothing is stored or sent until the visitor answers, and Accept and Decline carry equal weight.

In the docs: Add the website script · Privacy modes

Questions.

Is that legal advice?

No. It describes what the script does. Whether a banner is required for your site and audience is a decision for you and your counsel.

Can I use my own consent tool?

Yes. Use `data-consent="required"` and call `tapll.consent(true)` or `tapll.consent(false)` from your tool’s callbacks.

Other questions.

See who is on your app and site right now. No analyst, no query building.