More in Privacy and security
- Cookieless analytics and consent
- The compliance center explained
- Export your data and handle deletion requests
- What are the three collection tiers?
- Do I need a consent banner?
- Does TapCub honor Do Not Track and Global Privacy Control?
- What does the compliance center control?
- How do I set privacy rules per region?
- What does China mode do?
- How do IP truncation and data retention work?
- How do I export my raw data?
- How do I handle a data-subject (DSAR) request?
- How do I delete a site or my whole account?
- How do I keep personal data out of my analytics?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usShort answer
The script writes nothing to the browser — no cookie, no local storage. Visitors are separated by an HMAC of the IP address and user agent, combined with a salt. The address is used for that hash and for geography, then discarded; it is never stored on the event row.
A hash instead of a cookie
On the default tier, TapCub separates visitors with an HMAC of the IP address and user agent, combined with a salt. The script itself writes nothing to the browser. The address is used for that hash and for geography, then discarded — it is never stored on the event row.
Balanced vs strict
Two presets change how long the pseudonym lasts:
- Balanced keeps a site-level salt, so a returning visitor can be recognized across days and “new vs returning” works.
- Strict rotates the salt every day. Nobody is recognized across days; returning visitors are not reported.
Choose on ConfigurationSettingsPrivacy. Rows already stored are not rewritten when you switch.
Lower totals than a cookie tool usually mean it counted bots or multiple tabs; higher totals mean a banner blocked it. Trends match, totals do not — see why UV never matches.
Did this answer your question?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.