Problem
Header-only GPC checks miss broken preference wiring and vendor leakage.
Compliance · Hero API
Privacy / GPC API
What it does: End-to-end Global Privacy Control and preference verification — not header-only detection.
Problem it solves: Header-only GPC checks miss broken preference wiring and vendor leakage.
Who it is for: Privacy engineers · CMP implementers · Legal ops
Module
Solution
Trace preference signals through tracking config and downstream vendors with evidence.
Use cases
Developer
- Scan URL for GPC handling
- Regression tests in CI
- Vendor CMP verification
Business
- Prove GPC support to counsel
- Audit publisher inventory
- Pre-launch privacy checks
Overview
Verify preference → tracking config → downstream vendors → evidence. Built for sites that sell or share personal data and must process GPC signals properly.
Features
- Preference processing
- Downstream verification
- Continuous monitoring
Benefits
- Beyond header sniffing
- Vendor-aware evidence
Live example
Endpoint: /api/v1/privacy/gpc/scan — free public path available via Compliance X-Ray (real scan, not fabricated output).
curl -X POST https://hq.amberoneai.com/api/v1/privacy/gpc/scan \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"example":true}'Pricing
From $149/mo. Full plan matrix on /pricing — no invented discounts.
View pricingTrust
- Authentication: Bearer API key after signup
- Documentation: /docs
- Legal: Scores assist operational readiness — not a formal legal certification
- Status: See /marketplace/status for live probes
Next steps
FAQ
Is Privacy / GPC a legal certification?
Scores and findings assist operational readiness. They are not a formal legal compliance determination, government certification, or legal advice.
How do I get an API key?
Create an account at /signup, choose a plan on /pricing, then generate keys in your dashboard.
Where is the documentation?
Start at /docs. Product-specific OpenAPI and README links are listed on each API page.