Skip to main content

Policies Overview

A policy is the rulebook that defines what consent means on your property. Every consent receipt references the exact policy version that was active when the user decided.

What a policy contains​

  • Categories — the consent groupings shown to users (Necessary, Analytics, Marketing, Functional)
  • Purposes — specific data processing purposes within each category
  • Vendors — the third-party services assigned to each category
  • Region rules — which policy applies to visitors from which countries

Why policies are versioned​

If you add new vendors or change your data processing, you need to publish a new policy version. This:

  1. Triggers consent re-collection from affected users (their previous consent referenced the old version)
  2. Creates a clear audit trail — every receipt shows exactly what was consented to

Policy lifecycle​

Draft → Published → (Superseded by new version)

You can have one published policy at a time. A draft policy is invisible to users until published.

One policy per property​

Each property has one active policy. If you operate in multiple regions with different requirements (e.g. EU vs. US), use region rules to serve different content from a single policy.