cookiestatus.com

History

last_modified: suggest_edit

Changes to what browsers do by default, newest first. Each entry links to its source and to the parts of the comparison table it affects. Cookie Status started in November 2019; earlier entries are the milestones that shaped the protections it covers. Entries marked announced or in trial weren’t, or aren’t yet, the default for everyone.

Follow changes with the RSS feed.

2026

  1. Safari

    Safari 27.2 stops capping cookies on CNAME-hosted sites

    Cookies set by the response to a top-level navigation are no longer capped at 7 days when the site’s own hostname is a CNAME to another domain, such as a hosting provider.

    affects: cname cloaking · source: WebKit Features for Safari 27.2

  2. Safari

    Safari 27 blocks identity resolution services

    Cross-site requests to “ID graph” services, which link the same person across sites and devices, are blocked whenever “Prevent cross-site tracking” is on. Apple maintains the list of domains.

    affects: tracker blocking · source: Blocking identity resolution infrastructure (WebKit blog)

  3. Firefox

    Firefox 151 adds fingerprinting protection to Standard mode

    Firefox limits how much information about the device and browser is revealed to sites in its default mode, not only in Strict mode.

    affects: fingerprinting · source: Firefox 151 release notes

2025

  1. Safari

    CHIPS returns in Safari 26.2

    Partitioned cookies with the Partitioned attribute are supported again, after being removed in Safari 18.5 for further work.

    affects: 3rd-party cookies · source: WebKit Features in Safari 26.2

  2. Chrome

    Google retires most Privacy Sandbox technologies announced

    Topics, Protected Audience, Attribution Reporting, Related Website Sets and others are being phased out. CHIPS and FedCM stay.

    affects: 3rd-party cookies · source: Update on plans for Privacy Sandbox technologies

  3. Firefox

    Firefox 141 supports partitioned cookies (CHIPS)

    Third-party cookies can opt in to partitioning with the Partitioned attribute. Total Cookie Protection already partitions them, so this mainly helps developers write one cookie for all browsers.

    affects: 3rd-party cookies · source: Firefox 141 release notes

  4. Chrome

    Chrome keeps third-party cookies announced

    Google says Chrome will keep its current approach to third-party cookies and won’t add a separate prompt for users to choose. Third-party cookies stay enabled by default.

    affects: 3rd-party cookies · source: Next steps for Privacy Sandbox and tracking protections in Chrome

  5. Safari

    Safari 18.4 supports partitioned cookies (CHIPS)

    Cookies set with the Partitioned attribute work in third-party context, kept separate for each top-level site. The feature was removed again in Safari 18.5 (May 2025) and returned in 26.2.

    affects: 3rd-party cookies · source: Safari 18.4 release notes

2024

  1. Chrome

    Google drops its plan to phase out third-party cookies announced

    Instead of removing third-party cookies, Google proposes letting users make a choice in Chrome. The plan was itself dropped in April 2025.

    affects: 3rd-party cookies · source: A new path for Privacy Sandbox on the web

  2. Chrome

    Chrome restricts third-party cookies for 1% of users in trial

    A test of “Tracking Protection” blocks third-party cookies by default for a random 1% of Chrome users. The test ended when Google changed course.

    affects: 3rd-party cookies · source: Google shares update on next step toward phasing out third-party cookies in Chrome

2023

  1. ChromeEdge

    Chromium partitions third-party storage

    From Chrome 115, storage, service workers and communication APIs in third-party frames are partitioned by top-level site, rolled out gradually. Edge has the same behavior.

    affects: 3rd-party storage · source: Storage partitioning deprecation trial (Chrome for Developers)

  2. ChromeEdge

    Chrome 114 supports partitioned cookies (CHIPS)

    Third-party cookies can opt in to partitioning with the Partitioned attribute. Edge 114 followed days later.

    affects: 3rd-party cookies · source: Cookies Having Independent Partitioned State (CHIPS)

2022

2021

  1. Brave

    Brave skips known bounce trackers

    With “debouncing”, Brave notices when a link goes through a known tracking domain and navigates straight to the destination (desktop 1.32).

    affects: other · source: Debouncing (Brave privacy updates)

  2. Safari

    Safari 15 hides the IP address from known trackers

    Requests to known trackers no longer reveal the user’s IP address.

    affects: other · source: Safari 15 release notes

  3. Brave

    Brave announces ephemeral third-party storage announced

    Instead of blocking storage in third-party frames, Brave gives each one a temporary partition that is cleared when the user leaves the site. It was turned on by default later in 2021.

    affects: 3rd-party cookies, 3rd-party storage · source: Ephemeral third-party site storage (Brave privacy updates)

  4. Firefox

    Firefox 85 partitions network state

    The HTTP cache and other network state are kept separate for each top-level site, so “supercookies” stored there can’t track users across sites.

    affects: 3rd-party storage · source: Firefox 85 release notes

2020

  1. Safari

    Safari caps cookies from CNAME-cloaked subdomains

    Cookies set by HTTP response from a subdomain that is a CNAME alias for a third party expire after 7 days at most.

    affects: cname cloaking · source: CNAME cloaking and bounce tracking defense (WebKit blog)

  2. Brave

    Brave uncloaks CNAME trackers

    Brave 1.17 resolves the DNS of each request and blocks it if a CNAME record points to a domain on its blocklists.

    affects: cname cloaking · source: Brave 1.17.73 release

  3. ChromeEdge

    Chrome 86 partitions the HTTP cache

    Cached files are stored separately for each top-level site, so a third party can’t use the cache to recognize the same browser on different sites.

    affects: 3rd-party storage · source: Gaining security and privacy by partitioning the cache (Chrome for Developers)

  4. Safari

    WebKit's protections extend to all iOS browsers

    With iOS 14, Intelligent Tracking Prevention applies to every browser and in-app browser on iOS, since they all use WebKit. Only the user can turn it off.

    affects: other · source: Tracking Prevention in WebKit

  5. ChromeEdge

    Chrome 85 trims the referrer by default

    The default referrer policy becomes strict-origin-when-cross-origin, so other sites only see the origin of the referring page.

    affects: referrer · source: A new default Referrer-Policy for Chrome (Chrome for Developers)

  6. Firefox

    Firefox 79 clears data from redirect trackers

    Cookies and site data of known trackers are deleted daily unless the user has interacted with the site in the last 45 days.

    affects: 1st-party cookies, 1st-party storage · source: Firefox 79 release notes

  7. Safari

    Safari blocks all third-party cookies

    Safari 13.1 blocks third-party cookies for all domains, not only classified trackers, and caps all script-writable storage at 7 days of browser use without interaction.

    affects: 3rd-party cookies, 1st-party storage · source: Full third-party cookie blocking and more (WebKit blog)

  8. Edge

    New Edge ships with tracking prevention

    The Chromium-based Edge 79 is released with tracking prevention set to Balanced by default.

    affects: known trackers, 3rd-party cookies · source: Tracking prevention in Microsoft Edge

  9. Firefox

    Firefox 72 blocks known fingerprinters

    Requests to domains in Disconnect.me’s Fingerprinting category, when also listed as trackers, are blocked by default.

    affects: tracker blocking, fingerprinting · source: Firefox 72 release notes

2019

  1. Firefox

    Firefox 70 blocks social media trackers

    Requests to the most common social media trackers are blocked by default.

    affects: tracker blocking · source: Firefox 70 release notes

  2. Safari

    ITP 2.3

    Script-writable storage is deleted after 7 days without interaction on sites reached via known trackers, and document.referrer is trimmed for them.

    affects: 1st-party storage, referrer · source: Intelligent Tracking Prevention 2.3 (WebKit blog)

  3. Firefox

    Enhanced Tracking Protection on by default

    Firefox 69 blocks third-party cookies of known trackers and cryptominers for all users.

    affects: 3rd-party cookies, tracker blocking · source: Firefox 69 release notes

  4. Safari

    ITP 2.2

    Cookies set by script on pages reached from a known tracker with link decoration expire after 24 hours.

    affects: 1st-party cookies · source: Intelligent Tracking Prevention 2.2 (WebKit blog)

  5. Safari

    ITP 2.1

    Cookies set with document.cookie expire after 7 days at most.

    affects: 1st-party cookies · source: Intelligent Tracking Prevention 2.1 (WebKit blog)

2018

  1. Safari

    ITP 2.0

    Classified domains lose third-party cookie access immediately, unless granted through the Storage Access API or the pop-up compatibility fix.

    affects: 3rd-party cookies · source: Intelligent Tracking Prevention 2.0 (WebKit blog)

  2. Safari

    Storage Access API

    Embedded third parties can ask the user for access to their cookies.

    affects: 3rd-party cookies · source: Introducing Storage Access API (WebKit blog)

2017

  1. Safari

    Intelligent Tracking Prevention 1.0

    Safari starts classifying cross-site trackers on the device and restricting their cookies.

    affects: known trackers, 3rd-party cookies · source: Intelligent Tracking Prevention (WebKit blog)