Practical security for everyday technology.

A partitioned cookie keeps a separate jar for each top-level site

Two separate clear jars of plain wooden tokens on a desk beside a laptop, editorial metaphor for partitioned cookie storage.
AI-generated photographic illustration; not documentary photography.

The same chat service appears inside two unrelated websites. With an ordinary shared third-party cookie, the service may recognise the same browser across both contexts. A partitioned cookie changes the storage arrangement: each top-level site gets a separate context for that embedded service’s cookie.

MDN’s CHIPS explanation describes cookies stored with both a host key and a partition key associated with the top-level site. CHIPS stands for Cookies Having Independent Partitioned State.

A small example

Imagine a fictional support widget embedded by a museum and a bicycle shop. The museum’s widget context can remember a setting without that same partitioned cookie automatically carrying the setting into the bicycle shop’s context. This example describes the storage boundary, not the behaviour of any named real service.

Partitioning is also different from refusing to store the cookie at all. An embedded feature may still need state to work. The point is to constrain where that state is shared.

What it does not establish

A partitioned cookie is not a certificate that a service collects no other information. Accounts, requests and other data flows still need their own explanation. Browser settings and implementation support matter too. Do not infer complete anonymity from finding the word “Partitioned” in a developer tool.

If you maintain a website, test the embedded feature in the browsers your audience uses. Try a fresh session, a return visit and a visit through a different top-level site under your control. Record the expected behaviour before testing so that an accidental loss of settings is not confused with a privacy improvement.

For everyday browsing, the useful question is narrower: which site context can use this stored value? That makes a privacy explanation more concrete than saying only that a cookie is “necessary” or “third party.” It also leaves room to ask what the service does with the information after the browser sends a request.