Storage partitioning
Browsers key embedded storage by the top site so a tracker sees a separate store on each site.
In one line
Can't use the same embedded storage to recognize you across different sites
Browsers key embedded storage by the top site so a tracker sees a separate store on each site.
Cuts the main cross-site tracking path: a widget on site A and site B no longer shares one cookie or localStorage. Embeds can still track within one site, and workarounds shift to link decoration, redirects and server side IDs.
What it can and can't do
What the user does: Nothing. Your browser does it for you whenever a page is embedded.
It can
- Store data separately for each site that embeds it
- Still remember you on one site
- Ask for its own cookies back, if you allow
It cannot
- Share one stored copy across the sites that embed it
- Link a visit on one site to a visit on another through that storage
- Skip the Storage Access prompt where browsers require it
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 115 | 2023-07-18 | None |
| Edge | Supported | 115 | 2023-07-21 | None |
| Firefox | Supported | 103 | 2022-07-26 | None |
| Safari | Supported | 13.1 | 2020-03-24 | None |
| Safari on iPhone | Supported | 13.4 | 2020-03-24 | None |
| Chrome on Android | Supported | 115 | 2023-07-21 | None |
| Samsung Internet | Supported | 23.0 | 2023-10-18 | None |
How a site asks for it
| API | Browser behaviour keyed by (top-level site, frame site); use Storage Access API to opt out |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Per browser profile |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: No data exposed
Shape: none
How often: n/a
No individual data fields. The signal is the access itself.
Technical limits
- Third party frames get a different store on each top site
- Includes cookies (Firefox, Safari), localStorage, IndexedDB, Cache, BroadcastChannel, SharedWorker
- Chrome partitions storage but keeps unpartitioned cookies as a user choice
The story
What it is
Browsers give an embedded site a separate store on every site that embeds it, so trackers cannot link you.
For you
You get this for free. A tracker or like button embedded on two sites can no longer recognise you as the same person using its own stored data.
For makers
It is a big win for privacy and a loss for old style cross site tracking. Ad firms must move to other signals. Honest embeds, like logins and chat, may need to ask for access.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | An ad network embedded on two news sites sees two different, unlinked visitors instead of one person. | None named |
| social | A like or share button on a blog can no longer use its own cookie to see which other sites you visit. | |
| video | An embedded video player forgets your login on each site until it asks for access. | YouTube |
| enterprise | A support chat widget on a company site keeps a chat only for that site, not across the web. | Intercom |
| games | A game portal that embeds each game keeps game saves apart per portal. | Poki, CrazyGames |
| analytics | A measurement firm can no longer follow a visitor across client sites using embedded storage. | None named |
| security | A fraud service embedded on many sites loses a shared ID and must use other signals. | None named |
Risks
- Breaks some embeds
- Pushes trackers to fingerprinting
What the platform says
- MDN: State partitioning. Mozilla explains how Firefox splits stored data by the top site to stop cross site tracking.
- WebKit: Tracking Prevention. Apple describes how Safari limits cross site tracking, including how embedded storage is isolated.
Good uses and abuse
Legitimate uses
- Privacy by default
Known abuse
- Not applicable
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2020-03, Safari 13.1: Full third party cookie blocking and partitioned storage in ITP
- 2022-07, Firefox 103: Total Cookie Protection by default for all users
- 2023-07, Chrome 115: Third party storage partitioning rollout for storage and communication APIs
Related capabilities
Related
- Third-party cookies by browser (Nov 2026). Can recognise you across sites with embedded cookies, unless your browser blocks them
- CHIPS partitioned cookies. Can keep a cookie for an embedded service, separate for each site it appears on
- Storage Access API. Can ask to use its own cookies when embedded in another site
Sources
How well checked: Checked against real behavior.