Private State Tokens
Lets one site share a trust signal about a visitor with another without identifying them.
In one line
Can pass a small trust badge about you between sites without naming you
Lets one site share a trust signal about a visitor with another without identifying them.
Carries a one bit trust token to other origins so bots can be told from people without a login. Privacy Sandbox wind down affects its future.
What it can and can't do
What the user does: Nothing. It happens quietly in the background when the page loads
It can
- Store a token after a site decides you are probably a real person
- Show that token to another site so it can skip a bot check
- Carry one yes or no signal, with no name or account
It cannot
- Tell the other site who you are
- Work in Firefox or Safari
- Count on a long future, because Chrome is winding down the Privacy Sandbox
How it differs between platforms: Only Chromium browsers have it. Firefox and Safari do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 117 | 2023-09-12 | None |
| Edge | Supported | 117 | 2023-09-15 | 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 | Supported | 117 | 2023-09-12 | None |
| Samsung Internet | Supported | 24.0 | 2024-01-25 | None |
How a site asks for it
| API | document.hasPrivateToken(issuer), document.hasRedemptionRecord(issuer), fetch(url,{privateToken:{...}}) |
| Browser compat keys | api.Document.hasPrivateToken |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Lets one site share a trust signal about a visitor with another without identifying them.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
hasPrivateToken | boolean | None | true or false | per issuer |
redemption record | binary | bytes | signed 32 to 64 bytes | Not listed |
Technical limits
- Chrome and Edge only
- Limit of about 2 issuers per origin in Chrome
- Tokens are unlinkable by design
The story
What it is
A site can pass a hidden 'this is a real person' mark to another site, without your identity.
For you
You never see it. After you pass a check on one site, the browser may carry a trust token that another site can read as a yes or no. It may mean fewer puzzles asking you to prove you are human.
For makers
Fraud and anti-bot teams want to know a visitor looks like a person before they sign up or buy. The token lets a trusted issuer vouch for the browser, which lowers fake account and ad fraud. The wider Privacy Sandbox project has been scaled back, so its future is unsure.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A checkout page reads a token from an issuer that earlier saw you act like a normal person, then skips a CAPTCHA for you. | None named |
| ads | An ad network checks the token to filter out bot clicks and charge advertisers only for real viewers. | None named |
| games | A browser game lobby uses the mark to keep bots out of free signups and ranked queues without nagging players. | None named |
| social | A social site gates new account creation behind the token, so a bot farm cannot register thousands of accounts. | None named |
| shopping | A ticket seller uses it to let real fans into the queue while keeping scalper bots out. | Ticketmaster |
| analytics | A measurement vendor keeps traffic counts clean by excluding visits with no trust mark. | None named |
Risks
- Might label some real people as bots
- Unclear future
What the platform says
- Google Chrome: Private State Tokens. Google pitched it as a way for sites to share a trust signal about a visitor across sites without identifying them or using cookies.
Good uses and abuse
Legitimate uses
- Bot detection
Known abuse
- Cross site signal if issuers collude
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 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
- 2023-09, Chrome 117: Private State Tokens ships
- 2025, Chrome 155: Privacy Sandbox wind down coverage; status of PST unverified
Sources
How well checked: Inferred from related behavior.