Evidence JSON upload
Import evidence without building an API integration. Manual upload submits existing automation-generated evidence; it does not capture a journey.
Product features · Pre-launch
Evaluate consent. Investigate findings. Explain the outcome.
ConsentTrace ingests web evidence from third-party consent automation frameworks, evaluates consent behaviour and generates traceable reports.
Feature catalogue
Built around the questions your evidence needs to answer.
This describes the product workflow. Public launch and pilot availability are separate; supported features, regional profiles and integrations are confirmed before access.
API ingestion
Connect a supported evidence collector using the agreed schema and a scoped API connection. Automation currently produces the evidence; API submission is optional when JSON upload suits your workflow.
Evidence validation
Check payload structure and submission context. Missing optional artifacts can reduce assurance quality while leaving structured observations evaluable; evidence limitations remain visible.
Consent behaviour evaluation
Assess cookies, requests and other captured activity against consent observations, policy rules and approved technology classifications. Keep rule failures distinct from items that require review.
Technology Inventory
Use an organisation-wide approved classification library for cookies, scripts and request patterns. Match dynamic cookie names with supported wildcards and review unknown activity before approving a classification.
Classification review
Investigate observed technology activity and record category, purpose and regional-treatment decisions. Suggestions and collector metadata do not automatically become approved classifications.
Team review
Assign review work, record decisions and retain the context needed by privacy, QA and engineering teams. Roles and permissions are confirmed for the pilot scope.
Finding lifecycle
Track findings through investigation and remediation. Keep status changes and the evidence supporting verification in the review record.
Change and fix verification
Review later evidence for comparable property, environment, region, journey and consent-selection scope. Evaluable partial evidence can support verification; unable-to-evaluate evidence cannot prove a fix.
Regional policy context
Apply the configured policy profile to the observed evidence. Regional findings explain the evaluated rule scope without implying that every legal obligation has been checked.
Reports and structured results
Review findings and evidence references in regional reports and supported exports. Formats, integration options and report scope are confirmed before activation.
Traceable decisions
Follow the relationship between collected evidence, evaluations, findings and review decisions. Changes to classifications do not rewrite the originally captured evidence.
Future direction
Planned beyond the current web evidence workflow.
These are future capabilities. They are not currently offered as collection or testing options, and release dates and access terms have not been announced.
Mobile app support
Planned
Extend consent evidence evaluation and reporting to mobile applications alongside the current web workflow.
Customer-configurable AI testing
Planned
Build an internal AI agentic testing capability within ConsentTrace that customers can configure to carry out their consent testing journeys.
Browser extension
Planned
Capture data while you complete a journey manually, then generate an evidence JSON file. Download it or send it directly to ConsentTrace for evaluation.
Make evidence actionable