Illustrative sample
Consent Release QA Evidence Pack
This simulated example shows the proposed €49 deliverable. It is not a report about a real company or website.
Release summary
One high-priority regression is reproduced on 2 of 3 representative URLs: the same recognized analytics request appears before choice and after the automated “Reject all” action.
State comparison
| Representative URL | Default | After reject | Outcome |
|---|---|---|---|
| / | 2 tracker signals | 2 tracker signals | Review |
| /pricing | 2 tracker signals | 2 tracker signals | Review |
| /contact | 0 tracker signals | 0 tracker signals | No signal |
Example finding
Recognized analytics persisted after reject
Confidence: medium. Evidence: the same recognized request category appeared in fresh default and reject sessions. Recommended QA step: inspect tag consent requirements, publish the corrected container, then rerun the three URLs in a clean browser.
Review the complete deliverable
Open the self-contained, print-friendly report for all three simulated URLs, including timestamps, scan IDs, state evidence, findings, remediation, limitations, and the rerun window.
Open the full simulated HTML reportIncluded in a paid pack
- Three public URLs in fresh default, reject, and accept sessions
- Timestamped network, cookie-attribute, storage-key, and visible-control evidence
- Confidence-labelled remediation steps and a client-shareable HTML report
- One automated verification rerun within seven days
No checkout is live yet. Clicking the purchase-intent button after a free scan records anonymous demand only; it takes no payment and collects no email.
Run a free scan first