What is an analytics compliance centre?

What it controls

• Collection level — anonymous counts only, pseudonymous visitor IDs, or full identification after sign-in.
• Consent — whether to wait for consent before collecting, and what to do with events before it.
• Regional rules — stricter defaults for regions with stricter laws.
• Minimisation — truncating IPs, dropping values that look like emails or phone numbers, masking parts of pages.
• Retention — how long each kind of data is kept.
• Requests — finding, exporting and erasing one person's data.

Why one place matters

Privacy settings scattered across a tracking snippet, a tag manager and a database job drift apart, and nobody can say what the site actually does. A single place makes the configuration reviewable, makes changes auditable, and lets you prove to a regulator or a customer what was collected on a given date.

The compliance centre in TapCub

TapCub's privacy centre is always on: IP addresses are never stored and retention limits are always enforced; the settings tune how strict the rest is. Per site you choose the default collection tier, whether consent is required, how Global Privacy Control and Do Not Track are honoured, IP truncation, personal-data stripping, element-text capture, masked selectors, retention for events, autocapture records, profiles and consent receipts, and the cooling-off period before erasure runs.

Regional overrides apply different settings by visitor region. Presets — CNIL exemption, UK statistics exception, German DSK basic counter and GDPR full consent — write a configuration in one step and lock the fields they depend on; child mode and China mode lock their own. Each preset comes with a rationale template for your privacy policy, and every change, preset, export and request is kept in the compliance audit log.

Common mistakes

• Changing settings without updating the privacy policy. The two must say the same thing.
• Turning off retention limits for "later analysis". Aggregate reports remain; detailed records are what carry risk.
• No owner. Someone should review the configuration when the site enters a new market.

Related guides: GDPR-Compliant Analytics.