ScanBell technical evidence

Example Co. Consent Release QA Evidence Pack (simulated)

Fresh-browser consent-state observations prepared for engineering and privacy review.

Pack IDSB-20260801-0D1019E5D5
Generated2026-08-01T11:15:00.000Z
Rerun through2026-08-08T11:15:00.000Z

Scope and interpretation

This pack records automated browser observations for 3 public URLs. Each page was opened in fresh default, reject, and conditional accept contexts. Findings are technical QA signals, not legal advice, a compliance certification, or proof of a visitor's subjective consent.

No cookie values, browser-storage values, IP addresses, user agents, credentials, or authenticated content are included.

Executive summary

PageScoreCritical/highFindingsCompleted states
https://www.example.test/48223/3
https://www.example.test/pricing48223/3
https://www.example.test/contact100003/3

1. https://www.example.test/

Scan ID
00000000-0000-4000-8000-000000000001
Completed
2026-08-01T11:10:04.200Z
Duration
4200 ms
Third-party domains
1
Tracker signals
2

State evidence

StateCompletedConsent controlsReject actionRequestsCookiesTracker domains
DefaultYesaccept, reject, manage21analytics.example.test
RejectYesaccept, reject, managefound; clicked21analytics.example.test
AcceptYesaccept, reject, manage21analytics.example.test

Findings and remediation

highmedium confidence

1.1 Recognized analytics loaded before a choice

A recognized analytics request was observed in the fresh default visit before any consent interaction.

  • Request: analytics.example.test (example-analytics)

Recommended check: Confirm the request purpose and delay the tag until the visitor has made the relevant choice.

highhigh confidence

1.2 Recognized analytics persisted after reject

The automated reject control was found and clicked, but the same recognized analytics request remained observable in the fresh reject state.

  • Request: analytics.example.test (example-analytics)

Recommended check: Review CMP-to-tag consent requirements, publish the corrected container, and rerun this URL in a clean browser context.

2. https://www.example.test/pricing

Scan ID
00000000-0000-4000-8000-000000000002
Completed
2026-08-01T11:10:04.200Z
Duration
4200 ms
Third-party domains
1
Tracker signals
2

State evidence

StateCompletedConsent controlsReject actionRequestsCookiesTracker domains
DefaultYesaccept, reject, manage21analytics.example.test
RejectYesaccept, reject, managefound; clicked21analytics.example.test
AcceptYesaccept, reject, manage21analytics.example.test

Findings and remediation

highmedium confidence

2.1 Recognized analytics loaded before a choice

A recognized analytics request was observed in the fresh default visit before any consent interaction.

  • Request: analytics.example.test (example-analytics)

Recommended check: Confirm the request purpose and delay the tag until the visitor has made the relevant choice.

highhigh confidence

2.2 Recognized analytics persisted after reject

The automated reject control was found and clicked, but the same recognized analytics request remained observable in the fresh reject state.

  • Request: analytics.example.test (example-analytics)

Recommended check: Review CMP-to-tag consent requirements, publish the corrected container, and rerun this URL in a clean browser context.

3. https://www.example.test/contact

Scan ID
00000000-0000-4000-8000-000000000003
Completed
2026-08-01T11:10:13.100Z
Duration
3100 ms
Third-party domains
0
Tracker signals
0

State evidence

StateCompletedConsent controlsReject actionRequestsCookiesTracker domains
DefaultYesaccept, reject, manage10None observed
RejectYesaccept, reject, managefound; clicked10None observed
AcceptYesaccept, reject, manage10None observed

Findings and remediation

No scored findings were produced for this automated run.

Verification rerun

One rerun of the same URLs is included through 2026-08-08T11:15:00.000Z. Compare the new scan IDs and timestamps with this pack after remediation or deployment.

Method limitations

Results reflect the network location, browser build, timing window, and page state at the recorded timestamps. Geo-targeting, experiments, delayed tags, authenticated flows, and controls the automation could not identify may change what another visitor observes. Findings should be reviewed by the responsible engineering and privacy teams.