Introduction
Prepare an auditable GDPR evidence pack for a client, legal team, buyer review, or regulator inquiry using the GDPRChecker Evidence Center.
What it means
Evidence Center brings together scan completion, banner publication, consent records, script enforcement, and verified remediation events for one site.
Events are linked by hashes and stored append-only so a reviewer can detect an invalid sequence or altered record.
Export the timeline in PDF for review and CSV for analysis or client evidence repositories.
An evidence pack demonstrates operational controls and history; it is not a legal conclusion that the site is fully compliant.
Why it matters
A screenshot of a banner cannot show what happened before consent, after a release, or after a finding was fixed. An ordered evidence record is more useful in vendor and legal reviews.
Common mistakes
- Treating a copied snippet as installed without verifying a live runtime heartbeat.
- Placing the consent runtime after GTM, analytics, advertising pixels, or theme-injected scripts.
- Publishing a configuration change without testing a clean browser session and the Reject all path.
- Applying a broad blocking rule without reviewing the detected provider and category first.
Practical checklist
- Confirm domain ownership and open the site-specific Privacy Setup flow.
- Install or update the GDPRChecker runtime before non-essential tracking code.
- Publish the banner configuration and verify its live heartbeat.
- Test initial visit, Reject all, analytics-only, Accept all, and withdrawal in a private window.
- Run a compliance scan and keep the resulting evidence with the release record.
- Enable scheduled scans so later tag, plugin, theme, or campaign changes are detected.
How GDPRChecker helps
GDPRChecker reconciles scans, published configurations, consent records, and remediation verification into a site-specific evidence chain.
Use the export after a significant release, a scheduled scan alert, or a customer request for audit proof.