Privacy and compliance
TapCub counts visitors without cookies by default and keeps IP addresses off the event row. These guides explain the collection tiers, how regional rules work, and how to export or delete data when someone asks.
Guides in this category
Read the cookieless guide first — it defines the three tiers the other guides refer to.
Cookieless analytics and consent
By default the script writes no cookie and no local storage. Here is how visitors are still counted, what the three tiers change, and when a banner is needed.
6 min readLast updated Sep 19, 2026
Read moreThe compliance center explained
Every site has a compliance configuration that the collector reads on each hit. This guide walks through the switches, region by region.
7 min readLast updated Sep 27, 2026
Read moreExport your data and handle deletion requests
Exports are async jobs that produce a gzip JSONL file. Deletion runs through data-subject requests with a cooling-off period, or by deleting the site or account.
6 min readLast updated Sep 21, 2026
Read moreThree more places to look
The help center covers the common path. For SDK references, release notes or a real person, use one of these.
Chat with the team
Describe what you tried and what you saw. Replies come from the people who build TapCub, usually within a few hours on business days.
OpenDeveloper docs
Full references for the web script, the 7 SDKs, the server API, webhooks and MCP — with every parameter and default value.
OpenChangelog
What shipped each week, with links to the guide that explains the new behavior. Useful when a screen looks different from a guide.
Open