The Artifact Machine Privacy & Consent Scanner

An HTTP-based artifact that checks every privacy and consent compliance signal on a page: cookie consent banners, GDPR/CCPA signals, tracking scripts, consent mode, and privacy policy presence.

Use this Actor before a site launch, privacy compliance audit, or competitive privacy assessment. It gives teams a structured privacy analysis with prioritized issues ranked by severity.

Pulled from The Artifact Machine: generated, tested, and cleaned up by a human.

What It Checks

• Cookie consent banner: detection, consent management platform (CMP) identification
• Consent dark patterns: pre-checked optional cookies, missing reject button
• Tracking scripts: Google Analytics, GTM, Facebook Pixel, Hotjar, and 10+ other trackers
• Google Consent Mode: detection, v1 vs v2 signals, ad_storage and analytics_storage parameters
• Privacy links: privacy policy, cookie policy, terms of service, Do Not Sell / CCPA opt-out
• Compliance signals: GDPR, ePrivacy, CCPA indicators, GPC meta tag
• Forms: PII collection detection (email, phone, name fields)

Best For

• privacy compliance audits
• pre-launch consent checks
• GDPR and CCPA readiness assessments
• competitive privacy benchmarking
• agency client compliance diagnostics

Input

{
  "url": "https://example.com"
}

Output

The Actor writes one dataset item and an OUTPUT key-value record with:

• cookie consent banner analysis and CMP detection
• tracking script inventory and count
• privacy link presence (policy, terms, cookie, Do Not Sell)
• Google Consent Mode detection and version identification
• compliance score and composite privacy score
• prioritized issues with severity, impact, and how-to-fix guidance
• indicators of what requires a full browser for deeper analysis

Limits

• This Actor analyzes a single page per run from HTTP HTML alone.
• It does not use a browser, so JavaScript-rendered consent banners and CMP scripts that inject content dynamically may not be detected reliably.
• Window-global checks (OneTrust, Cookiebot, CMP objects) require a browser and are skipped.
• Pre-checked checkbox detection is limited to HTML source analysis.
• Some sites may block automated requests differently from real browsers.

Pricing

Use pay-per-event pricing based on completed scans rather than per issue. Suggested starting price: $1.00 to $2.00 per completed privacy scan after private runtime cost is measured.