Skip to main content

Compliance overview

OptSens is a consent management platform. It collects the visitor's cookie choice, blocks non-essential scripts until that choice is made, records each decision with its context, and gives you proof you can hand to an auditor. This page maps those features to the privacy work you do.

OptSens supports your compliance workflow. It does not make legal decisions for you. Which obligations apply to your site depends on your audience, your data and your own legal advice.

Which regime applies

A consent banner does not behave the same way for every visitor. Under the GDPR a visitor must opt in before non-essential cookies run. Under the CCPA/CPRA a California visitor can opt out after the fact. OptSens decides which behavior to show using geo rules: you map each region to a regulatory mode, and the banner switches per visitor based on detected location.

ModeBehaviorTypical region
GDPROpt-in. Non-essential scripts blocked until consentEU/EEA, UK
CCPAOpt-out. A Do Not Sell link, GPC honoredCalifornia
IABTCF 2.3 purposes and vendorsEU publishers using IAB
BasicOpt-in banner, behaves like GDPRRegions with no strict rule

Feature map

What you need to doOptSens feature
Get prior consent in the EUOpt-in banner, auto script blocking
Offer an opt-out in CaliforniaDo Not Sell link, GPC handling
Tell visitors which cookies you setCookie declaration
Let visitors change their mindPreference center
Keep proof of each consentConsent records
Produce a receipt for one visitorConsent proof
Handle data subject requestsDSAR
Know how long data is keptData retention

Where to start

Proving it later

With consent logging on, every consent choice is stored as a consent record with a timestamp, the categories the visitor chose, and a receipt ID. Without it only the counts are kept. You can view these in consent logs, export them, or generate a signed consent proof PDF for a single visitor. This is the evidence trail you produce if a regulator asks how a given visitor consented.

Questions about a specific compliance scenario: [email protected].