Introducing

Composer

The next evolution of Consent Checker. One prompt. Every compliance test your program needs — orchestrated, not rigid.

Act I

Consent Checker — geolocation, consent, journey, with checkpoints in between.

The same step cards you see in Composer today — built as one linear flow, left to right.

Consent Checker
The rigid workflow
Workflow
Consent Checker — reject-all flow
example.com
Geo / Proxy
Geo / Proxy
region: US-CA
Load Website
Load Website
wait: 10s
Capture Checkpoint
pre consent
phase: pre_consent
Consent Flow
reject all
action: reject_all
Capture Checkpoint
post choice
phase: post_consent
Browser-Use Journey
User journey
Browse like a normal customer
Capture Checkpoint
post journey
phase: post_journey
Analysis
Compliance review
CCPA/CPRA

Assess whether production behavior honors the user's consent choice and matches policy.

Linear. Predictable. Until the world changed.

Composer started with one simple question:

“Does this really cover every compliance use case?”

Act II

A brave new world for privacy compliance.

With the rising wave of privacy enforcement and new threats such as pixel litigation, we decided: not really.

CIPA
California pixel litigation wave
WESCA · ECPA
Any flow
Can contain risk — and it changes with every enforcement action

In this environment, any sort of flow can contain risk — and that changes with every enforcement action and every court decision.

Act III

So we blew up Consent Checker.

Each step card becomes its own building block — geo, consent, checkpoints, analysis — scattered and ready to recombine.

Workflow
Consent Checker — reject-all flow
example.com
Geo / Proxy
Geo / Proxy
region: US-CA
Load Website
Load Website
wait: 10s
Capture Checkpoint
pre consent
phase: pre_consent
Consent Flow
reject all
action: reject_all
Geo / Proxy
Geo / Proxy
region: US-CA
Consent Flow
reject all
action: reject_all
Browser-Use Journey
User journey
task: browse site
Capture Checkpoint
pre consent
phase: pre_consent
Capture Checkpoint
post choice
phase: post_consent
Capture Checkpoint
post journey
phase: post_journey
Analysis
Compliance review

Constituent parts. Infinite combinations.

And I'm proud to announce

Composer

We took everything you know and love from Consent Checker — geolocation, consent flows, user journeys, checkpoints, legal analysis — and made it composable. Ask a question. Get a suite of tests. All orchestrated.

The metaphor

Since the late 1500s, composers have been an integral part of music.

Composer doesn't play every instrument — it conducts the orchestra. One vision. Every part in sync.

“A conductor doesn't play every instrument — but they make the orchestra sing.”

Bach
Salieri
Mozart
Ask Composer

One simple question.

Composer prompt
Run Composer
The remix

Composer dynamically remixes every component into a suite of new tests.

Ask one question — get multiple workflows, each with its own left-to-right step canvas. Just like the product.

All at the push of a button.

Consent Checker runs. Got CIPA? Runs. Every workflow orchestrated — one click to launch the full suite.

Orchestration

All orchestrated by Composer.

Consent Checker runs. Got CIPA? Runs. Every workflow — conducted from a single prompt.

Composer

Conducting 3 workflows

CCPA/CPRAQueued
CCPA/CPRAQueued
CIPAQueued
3 workflows
CCPA/CPRA — opt-out flow (US-CA)Run
CCPA/CPRA — GPC honoring (US-CA)Results
CIPA — website tracking / replay check (US-CA)Results
Workflow
CCPA/CPRA — opt-out flow
example.com
Geo / Proxy
Geo / Proxy
region: US-CA
Load Website
Load Website
wait: 10s
Capture Checkpoint
pre consent
phase: pre_consent
Consent Flow
reject all
action: reject_all
Reload
Reload
Analysis
Compliance review
CCPA/CPRA

Assess opt-out parity and cookie behavior after reject-all.

Try Composer now.

Ask one question. Launch every test your compliance program needs. Consent Checker evolved — orchestrated for the enforcement landscape ahead.