Related Website Sets (retired)
A declared group of sites that could share cookies. Removal postponed to Chrome 152 to 153.
In one line
Can't let a group of related sites share cookies in Chrome anymore
A declared group of sites that could share cookies. Removal postponed to Chrome 152 to 153.
Let one organisation list a primary plus associated and service sites (up to 5 associated, 3 service) that were treated as same party for storage access prompts. Retired Oct 2025 with requestStorageAccessFor; Related Website Partition discontinued.
What it can and can't do
What the user does: Nothing. It would have happened when you moved between sites in the same group
It can
- Have let sites in one declared group share cookies
- Have allowed embeds to use cookies without a prompt for sites in the group
It cannot
- Run in Chrome 152 or later, where removal was postponed
- Work in Edge, Firefox or Safari
- Add sites that were not declared
- Share cookies with unrelated sites
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Removed | 153 | 2026-09-08 | Removal in progress |
| Edge | Not supported | Not available | Not listed | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Removed | 153 | 2026-09-08 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | document.requestStorageAccessFor(); related-website-sets.json on GitHub |
| Browser compat keys | api.Document.requestStorageAccessFor |
| 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 | Set definition valid while listed |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Set membership
Shape: object
How often: list updated by Chrome component
No individual data fields. The signal is the access itself.
Technical limits
- Primary site plus max 5 associated sites
- Needed a public GitHub submission
- Only Chrome ever shipped
The story
What it is
A list of sites owned by one group that were to share cookies. Retired.
For you
You never saw it. A company could list its own sites as one group. The browser would then let them share cookies without a prompt. It was retired in 2025.
For makers
Big brands with many domains wanted to keep login across them. The list was a small fix to cookie blocking. It also let a company decide who counted as the same owner, which worried privacy groups.
Where you see it
| Type | Example | Apps |
|---|---|---|
| media | A news company with several sites kept one login across them. | Gannett, Condé Nast |
| shopping | A retailer shared a cart across its brand sites. | Walmart, Target |
| games | A game company shared login across its store, forums and game sites. | Epic Games, Ubisoft |
| social | A social network used the group for one sign in across its apps. | Meta |
| ads | An ad network could have shown the same ad profile across sites of one brand. | None named |
| enterprise | A software firm shared session cookies among its app and help domains. | Atlassian |
Risks
- Retired
- Owners defined their own groups
What the platform says
- Google Chrome: Related Website Sets. Chrome pitched it as a way for sites of one organization to share cookies in limited, declared groups.
Good uses and abuse
Legitimate uses
- Brand family single sign on (historical)
Known abuse
- Cross-site cookie sharing between a company's domains
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 | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025-10, Chrome 141: Retirement announced including requestStorageAccessFor and Related Website Partition
- 2026-06, Chrome 152: Removal postponed to Chrome 152 (post dated Jun 10 2026)
- 2026-09, Chrome 153: requestStorageAccessFor approved for removal in 153; code removal in 154 to 155
Related capabilities
Related
- Storage Access API. Can ask to use its own cookies when embedded in another site
- Third-party cookies by browser (Nov 2026). Can recognise you across sites with embedded cookies, unless your browser blocks them
Sources
- Privacy Sandbox: Update on plans (Oct 17, 2025)
- Privacy Sandbox feature status page (updated Aug 14, 2026)
- Privacy Sandbox history and removal timeline (checked Oct 2, 2026)
How well checked: Checked against real behavior.