State Partitioning

Browsers traditionally key client-side state by the origin (or sometimes registrable domain) of the location a resource was loaded from. For example, the cookies, localStorage objects, and caches available to an iframe loaded from https://example.com/hello.html will be keyed by example.com. This is true regardless of whether the browser is currently loading resources from that domain as a first-party resources or as an embedded third party resources. Trackers have taken advantage of this cross-site state to store user identifiers and access them across websites. The example below shows how example.com can use its cross-site state (in this instance, cookies) to track a user across its own site as well as A.example and B.example.

Firefox's past cookie policies attempt to mitigate tracking by blocking access to some storage APIs (e.g., cookies and localStorage) for certain domains under certain conditions. For example, our "block all third-party cookies" policy will prevent all domains from accessing certain storage APIs when loaded in a third-party context. Our current default cookie policy blocks access in a third-party context only for domains classified as trackers.

State Partitioning is a different approach to preventing cross-site tracking. Rather than block access to certain stateful APIs in a third-party context, Firefox provides embedded resources with a separate storage bucket for every top-level website. More specifically, Firefox double-keys all client-side state by the origin of the resource being loaded and by the top-level site. In most instances, the top-level site is the scheme and eTLD+1 of the top-level page being visited by the user.

In the example below example.com is embedded in A.example and B.example. However, since storage is partitioned, there are three distinct storage buckets (instead of one). The tracker can still access storage, but since every storage bucket is additionally keyed under the top-level site, the data it has access to on A will be different from the data on B. This will prevent a tracker from storing an identifier in their cookies when visited directly and then retrieving that identifier when embedded in other websites.

The Privacy Community Group has a Work Item for Client-Side Storage Partitioning. This serves as an overview of the standardization efforts for storage partitioning in the individual standards affected. We intend to align our state partitioning implementation with these efforts as the Work Item is standardized.

• Network Partitioning: Enabled by default for all users since Firefox 85.
• Dynamic Partitioning: Enabled by default for all users since Firefox 103. Prior to that:
  • Since Firefox 86: Enabled for users that have "Strict" privacy protections enabled.
  • Since Firefox 90: Enabled in private browsing.

To prevent JavaScript-accessible storage APIs from being used for cross-site tracking, accessible storage is partitioned by top-level site. This mechanism means that, generally, a third-party embedded in one top-level site cannot access data stored under another top-level site.

• localStorage
• sessionStorage
• DOM Cache
• IndexedDB
• Broadcast Channel
• Shared Workers
• Service Workers

Networking-related APIs are not intended to be used for websites to store data, but they can be abused for cross-site tracking. As such, the following network APIs and caches are permanently partitioned by the top-level site.

• HTTP Cache
• Image Cache
• Favicon Cache
• Connection Pooling
• Stylesheet Cache
• DNS
• HTTP Authentication
• Alt-Svc
• Speculative Connections
• Fonts & Font Cache
• HSTS
• OCSP
• Intermediate CA Cache
• TLS Client Certificates
• TLS Session Identifiers
• Prefetch
• Preconnect
• CORS-preflight Cache
• WebRTC deviceID

Generally, if accessible storage is partitioned by top-level site, access to a third-parties unpartitioned cookies can still be granted if the Storage Access API is supported:

• using the Storage Access API.
• automatically, such as for third-parties providing federated login.

Details about automatic grants are provided in the Storage Access Heuristics section.

• Cookies

To improve web compatibility, Firefox currently includes some heuristics to grant unpartitioned access to cookies automatically to third parties that receive user interaction. These heuristics are intended to allow some third-party integrations that are common on the web to continue to function.

Opener Heuristics

• When a partitioned third-party opens a pop-up window that has opener access to the originating document, the third-party is granted storage access to its embedder for 30 days.
• When a first-party a.example opens a third-party pop-up b.example, b.example is granted third-party storage access to a.example for 30 days.

Redirect Heuristics

• If a site b.example redirects to a.example, then b.example receives storage access to its embedder a.example if both a.example and b.example have been visited and interacted with within the last 10 minutes. This storage access will be granted for 15 minutes.
• If a tracker tracker.example (as classified by the Enhanced Tracking Protection) redirects to a non-tracker a.example and tracker.example received user interaction as a first-party within the last 45 days, tracker.example is granted storage access to a.example for 15 minutes.

Third-party frames may use document.requestStorageAccess to request unpartitioned access to cookie through the Storage Access API. Once granted, the requesting party will gain access to its entire first-party cookies (i.e., the cookies it would have access to if visited as a first-party).

We encourage site owners to test their sites, particularly those that rely on third-party content integrations. There are several features in Firefox to make testing easier.

Here is an overview of the messages logged to the web console when interacting with storage in a third-party context. In the following examples, a.example is the top-level site which embeds the third-party frame b.example.

If a third-party iframe is granted storage access to the parent context, Firefox sets a permission. To revoke access you can clear the permission via the Site Information Panel in the permissions section under "Cross-site Cookies".

Disable Web Compatibility Features

Setting privacy.antitracking.enableWebcompat to false will disable all ETP and State Partitioning web-compatibility features. Disabling these features can be useful when testing, to ensure your website is fully compatible with the State Partitioning mechanism in Firefox, and it does not rely on temporary heuristics.

Features disabled by the pref include:

• Storage access heuristics: Unpartitioned access to cookies can only be acquired via the Storage Access API.
• Automatic storage access grants: document.requestStorageAccess will always prompt the user.
• SmartBlock's "unblock on opt-in" feature, which will allow certain trackers when users interact with them.
• Any temporary anti-tracking exceptions granted to websites via the skip-listing mechanism.

Disable Heuristics

The following preferences can be used to disable individual storage access heuristics via the config editor:

• Enable / disable the redirect heuristics: privacy.restrict3rdpartystorage.heuristic.recently_visited, privacy.restrict3rdpartystorage.heuristic.redirect
• Enable / disable the window open heuristics: privacy.restrict3rdpartystorage.heuristic.window_open, privacy.restrict3rdpartystorage.heuristic.opened_window_after_interaction

Disable Network Partitioning

Network partitioning can be disabled with the privacy.partition.network_state pref.

Disable Dynamic State Partitioning

To disable dynamic storage partitioning for all sites you can use the network.cookie.cookieBehavior pref:

Exempt specific origins from partitioning

Dynamic State Partitioning can also be disabled for specific origins with the privacy.restrict3rdpartystorage.skip_list preference. This pref holds a comma separated list of origins to exempt. The pref value should follow the following format: first-party_origin_1,third-party_origin_1;first-party_origin_2,third-party_origin_2;....

For example, to disable partitioning for tracker.example on example.com or social.example on news.example you would set the pref to the following:

https://example.com,https://tracker.example;https://news.example,https://social.example

You can use * as a wildcard for either the first or third party. For example, to disable partitioning for videos.example on all sites, or to disable all partitioning on unpartitioned.example, you would set the pref to the following:

*,https://videos.example;unpartitioned.example,*