Honest capability status for COKIQ.

Evidence: Scanner output, risk score, health score, detected cookies, scripts, policies, and scan date.

Why: COKIQ can verify product-side scan data for connected domains.

Evidence: Cookie policy inventory records, policy version, sync timestamp, and review-needed items.

Why: Inventory is generated from scanner findings and preserved for review.

Evidence: Timestamp, country/profile, category choices, banner version, policy version, and consent state.

Why: COKIQ records visitor choices and keeps operational evidence.

Evidence: Admin report view and authenticated exports combining scan, policy, consent, GPC, and blocker evidence.

Why: Phase 4 and Phase 6 are live and documented.

Evidence: Agency reporting path exists, but branding/export polish should be validated per agency rollout.

Why: Safe to discuss as beta, not as a fully mature white-label reporting suite.

Evidence: Runtime banner, category choices, storage, and consent updates.

Why: Core COKIQ banner workflow is live.

Evidence: Early denied defaults and updates for ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, and security_storage.

Why: Live COKIQ site and embeddable script carry the v2 signal mapping.

Evidence: Blocked script/embed runtime events and blocker summary evidence.

Why: Major known trackers and embeds are blocked/released based on consent state.

Evidence: More vendor-specific blocking/classification rules need ongoing research and QA.

Why: Long-tail tags change constantly; promising full coverage without testing would be unsafe.

Evidence: Geo/regulation profiles, regulations page, GPC/opt-out handling, and evidence receipts across EU/UK, US, India, Brazil, Canada, South Africa, Singapore, Gulf, China, Hong Kong, Malaysia, Indonesia, Philippines, Australia, New Zealand, Switzerland, Japan, South Korea, Thailand, Turkey, LATAM, APAC, and global default.

Why: COKIQ supports operational profiles and reporting for major regions while legal wording remains review-bound.

Evidence: Public regulation map and operational review workflow.

Why: COKIQ can support the operational workflow, but final legal wording and applicability need local review.

Evidence: Requires counsel-reviewed templates and translation/localization QA.

Why: Legal notices cannot be generated blindly for every country and sector.

Evidence: No certification approval is currently documented.

Why: Requires Google program approval; COKIQ can be Consent Mode compatible without claiming certification.

Evidence: IAB TCF is roadmap, not live production support.

Why: Publisher/ad-tech TCF strings require separate implementation, policy, and validation work.

Evidence: No audit report or certificate is currently published.

Why: These require formal third-party audit/certification work before public claims are allowed.

Evidence: COKIQ is a product evidence platform, not a law firm.

Why: Only qualified counsel can issue legal opinions or compliance certificates.

Evidence: Universal script and setup guidance exist; marketplace approvals are separate.

Why: Marketplace approval depends on each platform review process.