Evidence ingestion
Receive evidence through manual JSON, batch packages, temporary file integrations or a REST API.
- Canonical, versioned evidence schema
- Payload and duplicate validation
- Web, iOS and Android digital properties
The ConsentTrace platform
The independent assurance layer after your automation.
Submit evidence from external web or mobile automation. ConsentTrace validates it, evaluates consent behaviour, compares observed technologies with your inventory and creates reviewable regional outcomes.
Clear separation by design
Your automation decides whether the technical journey passed. ConsentTrace records whether the evidence is complete and whether the observed consent behaviour needs attention.
Platform architecture
Framework-independent in. Structured assurance out.
The evidence producer and result consumer remain external to ConsentTrace.
Evidence producers
Playwright, Selenium, Cypress, Appium, Maestro or custom automation.
ConsentTrace assurance
Validate → normalise → evaluate → compare inventory → create findings → review.
Results and reports
API, signed webhook, JSON, CSV, PDF or HolisticQA.
Automation resultPassed
Evidence statusComplete
ConsentTrace evaluationAttention required
Regional reportGenerated
Platform workflow
Every outcome remains connected to its source evidence.
Evaluation
Normalise submitted evidence and apply region-aware evaluation policies without changing the automation result.
- Consent-state behaviour evaluation
- Evidence completeness checks
- Versioned policy profiles
Findings and review
Turn observations into structured findings with evidence references and accountable decisions.
- Confirmed findings and potential issues
- Scoped muting and accepted decisions
- Automatic reopening when behaviour changes
Inventory governance
Compare observed cookies and technologies with the customer’s declared inventory.
- Unknown technology detection
- Declared versus suggested category
- Classification review history
Reports and results
Package assurance outcomes for people and downstream systems.
- Regional PDF assurance reports
- Result JSON and CSV findings
- Results API, signed webhooks and HolisticQA
Audit history
Maintain the relationship between evidence, policy versions, findings, reviews and outputs.
- Run-linked findings
- Decision history
- Evidence retention controls in development
Application view
Evidence runs keep technical results and assurance outcomes separate.
42Evidence runs
3Confirmed rule failures
7Potential classification issues
4Unknown technologies
Digital propertyRegionAutomationEvaluation
Storefront · WebUKPassedAttention
Account · iOSEUPassedClear
Shop · AndroidUS-CAFailedEvaluated
Manual ingestion model
Evidence can be evaluated before a permanent API integration is complete.
Review workflows
Classification decisions, muting and audit history are actively being productised.
Private deployment
Availability depends on technical discovery and commercial agreement.
Make evidence actionable