Chrome's August 2026 privacy disclosure changes

What Chrome announced

Google's official Chrome Web Store update says collected user data must be strictly necessary for the extension's disclosed single purpose; all data collection must be prominently disclosed regardless of whether it relates to that purpose; and developers must proactively disclose relevant data-handling changes after installation.

The same announcement prohibits prediction-market extensions and extensions designed to bypass safeguards or guardrails in generative-AI services. Those changes are separate from this page's privacy workflow.

What to do before enforcement

1. Trace every data category from browser access through transmission, storage, sharing, retention, and deletion.
2. Connect each collected field to the disclosed single purpose and remove collection that is merely speculative or convenient.
3. Reconcile code behavior with the listing, privacy form, privacy policy, onboarding, and contextual prominent disclosure.
4. Define how existing users will learn about relevant data-handling changes after installation.
5. Test consent-denied, signed-out, error, and uninstall paths using browser network inspection.

Observed: pageUrl sent when user clicks Analyze
Disclosure: what is sent, why, destination, retention, deletion
Mismatch to avoid: "No website data is collected"

What static analysis can and cannot help with

A package scan can surface request code, host access, sensitive browser capabilities, and contradictions with explicit developer answers. It cannot observe production payloads, backend retention, vendor contracts, whether users understood consent, or how a reviewer will apply policy.

Official source

• Chrome Web Store policy updates for 2026
• Chrome Web Store program policies

Human-reviewed 2026-07-29. Verify the live policy and store forms again when making a submission decision.