Third-party cookies in Chrome in late 2026: the cookies stay, Privacy Sandbox goes
Google keeps third-party cookies in Chrome and is removing most Privacy Sandbox APIs. What changed, the Chrome versions involved and what you can do.
Third-party cookies are staying in Chrome. Google confirmed on 22 April 2025 that it keeps its current approach to these cookies, and on 17 October 2025 it announced that it would retire most Privacy Sandbox technologies, the tools that were meant to replace them. Through 2026, Chrome releases have been removing those tools one by one.
What changed
- Third-party cookies stay. You choose whether to allow them in Chrome's Privacy and security settings. Incognito mode blocks them by default.
- No new cookie prompt. The standalone prompt that would have asked every user about third-party cookies will not be rolled out.
- Most Privacy Sandbox APIs are retired. Citing low adoption, Google is retiring Topics, Protected Audience, Attribution Reporting, Private Aggregation, Shared Storage, Related Website Sets, IP Protection and several others.
- A few parts stay. CHIPS, FedCM and Private State Tokens remain, and Google's status page lists the Storage Access API as supported.
The UK Competition and Markets Authority had supervised the Privacy Sandbox through commitments from Google. After Google decided not to deprecate third-party cookies, the authority released those commitments and closed the case on 17 October 2025.
Key dates
- 22 April 2025: Google keeps third-party cookies and drops the standalone prompt.
- 17 October 2025: Google announces the retirement of most Privacy Sandbox technologies.
- 13 January 2026: Chrome 144 announces plans to deprecate and remove Private Aggregation, Shared Storage and Protected Audience.
- 25 August 2026: Chrome 152 deprecates and removes the Private Aggregation API.
- 8 September 2026: Chrome 153 lists Protected Audience, Attribution Reporting, Shared Storage and Related Website Sets under deprecations and removals.
- Topics is marked "deprecate and remove" on Google's feature status page (last updated 14 August 2026).
What to do now
For most people nothing changes on screen: third-party cookies keep working in Chrome's normal windows unless you block them under Settings, Privacy and security. If you build websites, stop relying on the retired APIs; CHIPS, FedCM and the Storage Access API remain. How EU cookie consent rules may change is a separate question, covered in our article on the Council's Digital Omnibus position.
If you would rather not manage cookie settings yourself, Dazr Browser blocks ads and trackers, hides your device fingerprint and sends no telemetry. It is based on Chromium, free and in beta: download Dazr Browser.
Sources
- Google Privacy Sandbox: Next steps for Privacy Sandbox and tracking protections in Chrome (22 April 2025)
- Google Privacy Sandbox: Update on Plans for Privacy Sandbox Technologies (17 October 2025)
- Google Privacy Sandbox: Privacy Sandbox feature status (last updated 14 August 2026)
- Chrome for Developers: Chrome 144 release notes (stable 13 January 2026)
- Chrome for Developers: Chrome 152 release notes (stable 25 August 2026)
- Chrome for Developers: Chrome 153 release notes (stable 8 September 2026)
- UK Competition and Markets Authority: Investigation into Google's 'Privacy Sandbox' browser changes (case closed 17 October 2025)
For information only, not legal advice. Last updated 7 November 2026.
Also available in: Nederlands, Italiano, Deutsch, Français, Español, Polski, Português, Română, Čeština, Slovenčina, Dansk, Svenska, Norsk bokmål