Skip to Content
Platform.Ontology

Third-party cookies by browser (Nov 2026)

Whether an embedded site can set and read its own cookies on other sites, which varies by browser.

Used to track youTracking across apps and sitesBefore the visitWeb browsersBefore you visitWhile you use it

In one line

Can recognise you across sites with embedded cookies, unless your browser blocks them

Whether an embedded site can set and read its own cookies on other sites, which varies by browser.

Third-party cookies are how ad networks recognise the same person across sites. Safari blocks them, Firefox partitions them, Brave blocks them, Chrome leaves them on by default (user choice) and blocks them in Incognito.

What it can and can't do

What the user does: Nothing. It happens when a page with ads or embeds loads

It can

  • Set and later see its own cookie from inside a page on another site
  • Link your visits across the sites that embed it
  • Keep working in Chrome, where these cookies stay on by default
  • Ask the browser for access if it was blocked (Storage Access prompt)

It cannot

  • Set these cookies in Safari, which blocks them
  • Share one cookie across sites in Firefox, which keeps a separate jar per site
  • Use them in Incognito windows in Chrome
  • Get through in Brave, which blocks them

How it differs between platforms: Safari and Brave block them, Firefox splits them per site, and Chrome allows them by default but blocks them in Incognito.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported512016-05-253PC allowed by default; blocked in Incognito
EdgeSupported162017-10-17Blocks classified trackers only
FirefoxRemoved1032022-07-26Partitioned by default
SafariRemoved13.12020-03-24Blocked entirely
Safari on iPhoneRemoved13.12019-09-19None
Chrome on AndroidSupported512016-06-08Allowed by default
Samsung InternetSupported5.02016-12-15Allowed by default, Smart Anti-Tracking blocks some

How a site asks for it

APIdocument.cookie in iframes; Set-Cookie with SameSite=None; Secure; Storage Access API
Browser compat keyshttp.headers.Set-Cookie.SameSite
How access is grantedsettings
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsCookie lifetime per cookie; Chrome caps at 400 days
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Cookie jar per top-level site (partitioned) or global
Shape: object
How often: continuous

FieldTypeUnitRangePrecision
cookiestringbytesup to 4096 per cookien/a

Technical limits

  • Safari: blocked for all, no exceptions except Storage Access API
  • Firefox: Total Cookie Protection partitions per top-level site by default (June 2022, Firefox 103)
  • Chrome: kept on by default; no deprecation prompt after the April 2025 decision; Incognito blocks by default
  • Edge: Tracking Prevention blocks classified trackers, not all

The story

What it is

Whether an embedded site can store cookies on other sites, which depends on which browser you use.

For you

You never see these cookies, but they decide whether an ad for boots follows you from a shoe shop to a news site. In Safari and Firefox it mostly cannot. In Chrome it still can, unless you turn it off in settings.

For makers

Ad networks use these cookies to recognise the same person across sites for targeting, frequency caps and conversion counting. Sites also use them for legitimate embeds like logins and payments. When a browser blocks them, makers must switch to first-party data or new APIs.

Where you see it

TypeExampleApps
adsA retailer's ad network sets a cookie when you view boots, then recognises you on a recipe blog and shows the same boots.Google Display Network, Criteo
socialA Like or Share button embedded on a news article recognises your logged-in account and counts the visit.Facebook, X
videoAn embedded video on a blog remembers your player settings and view history through the video host's own cookie.YouTube
gamesA browser game embedded in a portal page saves your progress under the game host's cookie, which breaks when the browser blocks it.itch.io
paymentsA card check inside a frame on a shop page relies on the bank's cookie to recognise a trusted device.Stripe
securityA bot defence service sets one cookie across many customer sites to spot a scraper hopping between them.Cloudflare
analyticsA marketing platform ties an ad click on one site to a purchase on another to report which campaign worked.Google Ads

Risks

  • Cross-site profiles of your habits
  • Settings differ by browser, so protection is uneven

What the platform says

Good uses and abuse

Legitimate uses

  • Embedded video, chat, SSO, payment frames
  • Ad measurement

Known abuse

  • Cross-site profile building by ad networks
  • Silent identifiers synced across domains

Scores

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

History

  • 2020-03, Safari 13.1: Full third-party cookie blocking
  • 2022-06, Firefox 103: Total Cookie Protection default for all users
  • 2024-01, Chrome 120: 1% of Chrome users had third-party cookies restricted (testing)
  • 2024-07, Chrome 127: Google proposed user choice instead of deprecation
  • 2025-04, Chrome 135: Google confirmed no standalone prompt; users keep the Settings choice
  • 2025-10, Chrome 141: Oct 17: Google retired most remaining Privacy Sandbox APIs; third-party cookies stay

Sources

How well checked: Checked against real behavior.

On this page