Skip to Content
Platform.Ontology

Top-level storage access (requestStorageAccessFor)

Lets a top-level page request cookie access on behalf of related embedded sites.

Asks you firstFiles and storageStorageWeb browsersWhile you use it

In one line

Can ask Chrome to let related embedded sites use their cookies, if you allow

Lets a top-level page request cookie access on behalf of related embedded sites.

Allows a page to unlock third-party cookies for sites in the same Related Website Set. Chrome only and deprecated; its use hints at cross-site identity joining.

What it can and can't do

What the user does: You tap a button on the page, then answer the Chrome prompt if one appears.

It can

  • Ask for cookie access for related sites embedded in the page
  • Skip the prompt when the sites are in the same Related Website Set
  • Use that access after you allow it

It cannot

  • Do it in Firefox or Safari
  • Reach unrelated sites
  • Get access if you choose Block

How it differs between platforms: Chrome and Edge only. Firefox and Safari do not have it.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported1192023-10-31Deprecated
EdgeSupported1192023-11-02None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported1192023-10-31None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APIdocument.requestStorageAccessFor(origin); permission top-level-storage-access
Permission nametop-level-storage-access
Browser compat keysapi.Document.requestStorageAccessFor
How access is grantedprompt
What the user seesChrome only: prompt unless the sites are in the same Related Website Set.
Needs a secure context (HTTPS)Yes
Needs a user gestureYes
How long it lastsPer top-level site
How to take it backSite settings
Inside an iframeNot applicable

Typical flow

  1. User gesture on top-level page
  2. requestStorageAccessFor('https://embed.example')
  3. Chrome checks Related Website Set
  4. Embedded requests then carry cookies

Data you get

What comes back: Grant outcome
Shape: boolean
How often: one-shot

No individual data fields. The signal is the access itself.

Technical limits

  • Same Related Website Set only
  • Chrome only, deprecated

The story

What it is

Lets a main page ask the browser to share cookies with its related embedded sites.

For you

You might see a prompt asking if related sites can share your sign in. Say yes and it works smoothly across a company's brands. Say no and you may need to log in again.

For makers

It helps companies with several linked sites keep one sign in. It is a narrow path that browsers allow for related sites only. It is not meant for general ad tracking.

Where you see it

TypeExampleApps
enterpriseA company with several brand sites lets one login work across all of them.None named
shoppingA store group shares your cart and login between its regional shops.None named
mediaA media company keeps a subscription active across its linked news sites.None named
gamesA game publisher keeps one account across its game and community sites.None named
paymentsA payment provider recognises you across a merchant's linked checkout sites.None named
adsAn ad firm hopes to use it for tracking, but browsers limit it to closely related sites.None named

Risks

  • Cross site data sharing
  • Easy to approve by habit

What the platform says

Good uses and abuse

Legitimate uses

  • Brand-owned sites sharing sessions

Known abuse

  • Cross-site identity joining

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2023-10, Chrome 119: requestStorageAccessFor ships with Related Website Sets

Sources

How well checked: Based on official documentation.

On this page