TapCub is live — analytics, insights and live chat, free on one platform
Help center

The 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.

Privacy and security3 min readLast updated Sep 27, 2026TapCub team

Where it is and who can edit 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.

The page notes that compliance mode is always on. Address truncation, personal-data stripping and expiry deletion run for every site; this screen decides how strict each one is.

The top section sets the project default collection tier (1, 2 or 3, explained in the cookieless guide) 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 and is described in export and deletion.

Regional rules

Regions are derived from the country of the address before it is discarded (and for the US, whether the state is California). Each region rule can override the tier, the consent requirement, IPv4 / IPv6 address truncation, and the geography granularity:

RegionDefault rule
EEA, UKInherits the project default; when the last 30 days have EU / UK visitors, the compliance center suggests enabling IP truncation for these regions only
US-CaliforniaInherits project default; opt-out honored
Rest of USInherits project default
China (CN)Inherits project default; China mode adds further rules (below)
OtherInherits project default

A blank field inherits the project default. Global Privacy Control and Do Not Track are honored in every region and force tier 1 for that hit.

China mode

China mode is added on top of regional rules; it does not replace the EEA rule. When it is on, the SDKs wait for explicit consent before initializing, the cooling-off period for erasure requests defaults to 7 days instead of 3, and the China export counter, data-subject deadline and child-related fields become available. Child mode forces tier 1, writes no identifier and shortens raw-row retention.

Address truncation, stripping and retention

  • Address truncation — off by default. When needed, IPv4 can drop its last 1 or 2 bytes before the geo lookup and IPv6 can be cut to a /64, /56 or /48 prefix, optionally for some regions only (for example the EU / UK). The CNIL exemption preset forces at least 2 bytes for IPv4 and /64 for IPv6. The country is always taken from the full address; truncation only affects region / city precision. Geography can be city, country or none. The address itself is never written to the event.
  • Stripping — when enabled, strings that look like an email or a phone number in event properties are replaced with a placeholder. Autocapture does not capture visible text by default. Email and phone passed at login stay out of the profile unless encrypted contact storage is enabled.
  • Retention — defaults inside the compliance config are 12 months for events, 90 days for autocapture, 24 months for profiles and consent receipts. The effective value is capped by your plan: 6 months on Free, 12 on Pro, 24 or more on Max and Ultra. A scheduled job deletes expired rows.

Retention changes apply going forward and to existing rows: lowering it deletes older rows on the next scheduled run. Export first if you need them.

Presets and member masking

Two presets set several fields at once: pseudonymous statistics without consent and identified collection with full consent. Fields set by a preset are locked until you release it, so an Admin cannot accidentally weaken one switch.

Separately from collection, what each member sees on reports is controlled by display masking — none, partial or full — per role and per member. That lives on the Members page and is covered in Team and roles. The product overview is on Privacy and security.

Did this answer your question?

We use your answers to fix and expand this page.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics