Scan baseline
Latest scan status, health score, risk score, policy sync metadata, and cookie/script findings where available.
COKIQ docs
Understand COKIQ Evidence Reports for scan baseline, scanner-synced policy inventory, consent receipts, regulation profiles, GPC signals, banner and policy versions, blocker evidence, and exports.
Agencies, compliance teams, marketing operations, legal reviewers, leadership, and buyers checking what COKIQ can prove today.
These are the product-side evidence areas COKIQ can surface when the site has the required scan, banner, consent log, and blocker data.
Latest scan status, health score, risk score, policy sync metadata, and cookie/script findings where available.
Scanner-synced cookie and policy records that show which website evidence was reviewed instead of relying on manual copy alone.
Visitor choice evidence including country/profile context, category choices, consent timestamp, banner version, and policy version where captured.
Global Privacy Control and opt-out related evidence when the visitor/browser signal is present and relevant to the configured profile.
Tracker and iframe blocking evidence showing what COKIQ held back before consent and what was released after consent.
Authenticated report exports in JSON/PDF-style output, plus dashboard CSV for operational and agency handoff.
Step 1
Run or review the latest website scan so the report begins with real detected cookies, scripts, policy links, and risk signals.
Step 2
Confirm the cookie and policy inventory reflects what the scanner found, then flag unknown providers or review-needed items before exporting.
Step 3
Check that accept, reject, and custom choices are recorded with the right country/profile context, category choices, banner version, and policy version.
Step 4
Review whether GPC/opt-out signals and tracker or iframe blocking evidence exist for the tested sessions and configured profiles.
Step 5
Use dashboard reports, JSON/PDF-style exports, or CSV evidence depending on whether the recipient is an agency client, marketer, leadership team, or legal reviewer.
Step 6
Use the report as proof of operational setup and product behavior, then hand legal interpretation and country-specific policy review to qualified counsel.
It brings together scan baseline, policy inventory, consent receipts, regulation profile context, GPC signals where observed, banner and policy versions, blocker evidence, and export-ready report data.
No. Reports organize operational evidence and product behavior. Legal conclusions, country-specific policy wording, and regulatory interpretation require qualified review.
GPC evidence appears when the visitor or test browser sends the signal and the configured profile records it. Empty evidence usually means the signal was not observed in that test session.
Yes. Agencies can use reports for recurring scan review, consent proof, blocker evidence, policy inventory handoff, and client action planning. White-label report branding remains Beta.
No. Evidence exports are authenticated because they can contain domain, consent, and operational evidence. Public docs explain the output, but report data stays protected.