文章
What does a free US-baseline cookie audit prove vs paid EU or California scans?
Compare ConsentProbe’s free US-baseline visit with paid EU fresh/reject/accept and California GPC off/on scans so teams pick the right evidence pack.
In brief
A free US-baseline cookie audit records one browser visit outside California: cookies, requests, and screenshots for that visit profile. It does not produce GDPR reject conclusions or California GPC conclusions. Paid EU runs isolate fresh, Reject All, and Accept All. Paid California runs compare GPC off with GPC on. Pick the product whose scenarios match the claim you need to evidence.
Hard boundary
This page explains product scope in technical terms. It is not a legal opinion, certification, fine estimate, or a guarantee of legal approval. Locale and timezone settings do not replace regional IP evidence when you claim an EU or California result.
Short answer
Free US-baseline proves what that one non-California visit observed before you treat the report as a format and wiring check. Paid EU proves whether fresh, reject, and accept states change cookies and pixels on an EU-context path. Paid California proves whether GPC-off and GPC-on visits differ on a California-facing path.
If marketing claims “we honor Reject All in the EU” or “we honor GPC in California,” a free US-baseline report alone cannot carry that claim. Use the matching paid regional product, or run an equivalent DIY pack with the same isolation rules.
Scope comparison
Keep the table next to pricing when you choose a run. The rows describe observable scenarios, not legal outcomes.
| Product | What the run covers | What it does not prove |
|---|---|---|
| Free US-baseline | One browser visit outside California with cookies, requests, CMP surface, and screenshots | EU reject/accept behavior; California GPC off/on deltas; GDPR or CPRA conclusions |
| Paid EU | Isolated fresh, Reject All, and Accept All visits on an EU-context path | California GPC results; a legal determination that processing is lawful |
| Paid California | Matched GPC-off and GPC-on visits on a California-facing path | EU reject/accept results; a legal determination about sale or sharing |
When to use which pack
Start with free US-baseline when you need a saved technical record, a sample of report layout, or a first look at tags that fire before any regional claim. Move to paid EU when engineering must show reject versus accept on an EU path. Move to paid California when the claim is GPC honor or sale-or-share-style suppression.
- Write the claim in one sentence (example: Reject All blocks Meta on EU product pages).
- Match the claim to the table row whose scenarios can observe that claim.
- If only free US-baseline is available, label the report as a US-baseline technical record and do not extend it to GDPR or GPC conclusions.
- Keep screenshots and exports labeled by product and scenario so reviewers do not mix packs.
Evidence and soft CTA
Every regional conclusion in a ConsentProbe report should point at request, cookie, or screenshot IDs from the scenarios that produced it. The sample report shows that citation layout with synthetic data.
Need the EU fresh/reject/accept pack or the California GPC off/on pack after a free format check? Open pricing for the listed regional products. Free US-baseline remains available after sign-in for the non-California baseline visit.
FAQ
Does free US-baseline equal a GDPR audit?
No. Free US-baseline is one non-California visit. GDPR-oriented reject and accept proof needs the paid EU scenario pack with EU-context evidence.
Does free US-baseline prove GPC works?
No. GPC conclusions need matched GPC-off and GPC-on visits on a California-facing path.
What does paid EU actually run?
Isolated fresh, Reject All, and Accept All browser visits so you can compare pre-choice and post-action cookies and requests.
What does paid California actually run?
Paired GPC-off and GPC-on visits so you can compare sale-or-share-style traffic and cookies under the signal change.
Can I invent traffic volumes from these reports?
No. Reports describe observed technical evidence for the saved runs. They do not estimate site-wide volumes or legal risk scores.
Related guides
Use the reject leftovers and GPC claims pages when a regional pack shows a mismatch, and the pre-consent checklist before you widen scope.
- Pre-Consent Cookie Audit: A Storefront Checklist
- Reject All Still Tracking: What to Check After You Say No
- GPC vs CMP Claims: How to Spot a Mismatch
- First-party vs third-party cookies before consent: what should you check?
- What does California SB 690 change for website tracking lawsuits?
- Reject All vs Accept vs GPC: A Scenario Matrix for Shopify Stores
- ConsentProbe methodology
- Sample report
- Pricing and listed regional products
Sources
These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.
保存一次美国基线技术记录
完成自行检查后，可以跑一次免费美国基线审计：在加州以外做一次浏览器访问，把 Cookie、请求和截图存成证据。这次访问不会跑欧盟拒绝/接受，也不会跑加州 GPC。欧盟、加州和 Global 2 可在登录后的账单页购买。