More in Privacy and security
- Cookieless analytics and consent
- The compliance center explained
- Export your data and handle deletion requests
- How does TapCub count visitors without cookies?
- What are the three collection tiers?
- Do I need a consent banner?
- Does TapCub honor Do Not Track and Global Privacy 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
It sets the project collection tier, whether consent is required (and whether events queue or drop before it), and the visitor opt-out switch. Owners and Admins can edit; everyone else reads. Changes apply on the next hit, with no deploy.
Where it is and who edits it
Open Compliance center from the site menu (the project path is settings/privacy). Owners and Admins can edit; everyone else can read. After a save, the collector picks up the new rules on the next hit — there is no deploy. Compliance mode is always on: address truncation, personal-data stripping and expiry deletion run for every site, and this screen decides how strict each one is.
Tier, consent and opt-out
The top section sets the project default collection tier (1, 2 or 3, explained in collection tiers) and whether consent is required. Consent has three purposes — analytics, functional, marketing — and a before-consent behavior: queue (default) or drop.
Opt-out is a collection switch a visitor can flip from your site; its scope defaults to every device of that person and can be limited to the current device. It is not the same as a data-subject restrict request, which has a cooling-off period — see export and deletion.
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.