Does your site need a notice, a browser choice or both?
List the information your site uses and the optional browser features visitors can control. Write a notice that reflects the first and check that your site follows the second.
Which job needs a notice, and which needs a control?
A notice explains what you do with information. A preference control lets the person make a choice. The code on your site still needs to carry out that choice.
A workshop site might use a contact address for a booking confirmation and an optional audience counter to measure visits. The two have different jobs. List what each service receives and where it runs before deciding how to describe and control it.
How can you tell if a browser choice changes anything?
Check what the page loads before a choice, after a decline, and after the person changes their mind. For a tag you designated optional, verify its actual browser activity against your intended settings.
A tag can send a request without leaving a cookie. If you later test, use an isolated copy with fictional data and local or test destinations you control, with no live tags or customer accounts.
Compare tools
Scroll the table sideways to read every column.
| Tool | What it helps you doNotices, scans or visitor choices. | What to check on the siteHow a visitor choice affects an optional feature. | What the plan countsDomains, scanned pages or traffic. | What to keep for a changeRecords and notes to review when you move. |
|---|---|---|---|---|
| Termly | Policy generator, cookie banner and preference center. | Configure Auto Blocker and verify the individual optional tags. | Free lists one site, one basic legal policy and 10,000 monthly banner views. | Keep your data inventory and know which policy version is published. |
| iubenda | Privacy and cookie policy generator plus a separate preference tool. | Set up prior blocking and verify optional tags. | Essentials includes 25,000 monthly pageviews per site. Check extra usage rules. | Keep an independent service inventory. The FAQ limits use of paid policies after nonrenewal. |
| Cookiebot | Cookie scan, banner and ways to reopen preferences. | Automatic blocking depends on setup and scan classification. | Free lists one domain and up to 50 scanned subpages. Confirm eligibility. | Check consent log download access and retain your own tag inventory. |
| CookieYes | Show a choice banner and record choices. | Check optional scripts before and after a choice and after changing it. | Counts monthly page loads with the script. Check overage or banner pause. | Keep dated settings and plan-available consent CSVs. |
| Complianz | Configure a WordPress banner and supported script integrations. | Check which plugin loads the optional embed and what replaces it. | Premium WordPress pricing tiers count covered websites. | Keep dated configuration snapshots and any separate plan-available records. |
| Osano | Manage website consent choices and related script categories. | Check actual script behavior in each choice state. | Counts visitors requesting the consent library by 24-hour period. | Keep classifications, settings and the records available to your plan. |
| Didomi | Configure a consent notice and connect choices to supported tags. | Check which systems can load a tag and how each follows the choice. | Ask what the quote measures for your sites and needed features. | Keep notice settings and tag mapping. Batch export excludes guests by default. |
| Usercentrics | Show a website consent banner and map choices to services. | Check each service’s behavior when the visitor changes its setting. | Web CMP lists sessions using a 30-minute rule. Check domain limits. | Keep configuration and confirm the individual history export path. |
| Transcend | Coordinate request workflows, preference changes and consent tools. | Confirm the right person and which systems a request can affect. | Check annual contract units for request runs, preferences and sessions. | Keep routing rules, review history and confirmed audit records. |
| DocuSeal | Collect signatures and keep a record of signing events. | Check recipient roles and completion before storing the record. | Check web seats and API usage per signed submission. | Keep the completed document, certificate and template. |
Which limits should you count before choosing a plan?
Count domains, distinct page addresses and page loads or banner views as separate numbers. Each provider uses its own units.
Check how often scanning runs, whether you can export the records you need, and what happens when traffic or page counts exceed the plan.
How can you practise the visitor journey on paper?
Draw a fictional workshop site and a browser that has never visited it. Use no accounts, scripts or actual visitor information.
- Visit and declineLeave the optional counter off before any choice and after declining. The public schedule remains readable.
- Change preferences laterDraw the link the visitor uses to allow the counter, then reopen it to withdraw that choice.
- Separate future behavior from past dataOn the next page draw no new counter activity. Leave any previously sent information as a separate question to handle in your data practices.