Hashed email as identity
A SHA-256 hash of an email lets ad platforms recognise a person without the plain email.
In one line
Can recognize you across sites by a scrambled version of your email
A SHA-256 hash of an email lets ad platforms recognise a person without the plain email.
Normalised lowercase email hashed with SHA-256 is accepted by Meta, Google, LinkedIn and TikTok for matching. Hashing is deterministic, so the same email gives the same value everywhere. The FTC stated in July 2024 that hashing does not make data anonymous.
What it can and can't do
What the user does: You sign in, check out or subscribe with your email on a site
It can
- Turn your email into a scrambled code that stays the same everywhere
- Share that code with ad partners
- Match you across sites and devices where you used the same email
It cannot
- Give out your plain email in the code, but the code can be matched if a company already has your email
- Match you if you use a different email on each site
- Work without you entering the email somewhere
- Be cleared like a cookie, since it stays the same until you change your email
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | Not browser dependent |
| Edge | Supported | 1 | Not listed | Not browser dependent |
| Firefox | Supported | 1 | 2004-11-09 | Not browser dependent |
| Safari | Supported | 1 | 2003-06-23 | Not browser dependent |
| Safari on iPhone | Supported | 1 | 2007-06-29 | Not browser dependent |
| Chrome on Android | Supported | 1 | Not listed | Not browser dependent |
| Samsung Internet | Supported | 1 | 2013-04-27 | Not browser dependent |
How a site asks for it
| API | Pixel advanced matching fields, Conversions APIs, Customer Match uploads |
| 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 | Lives on platform side for the account lifetime |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: SHA-256 hex digest of normalised email
Shape: hash
How often: per form submit or login
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
digest | hash | hex | 64 chars | 256 bit |
Technical limits
- Needs the person to have given or entered an email
- Match rates vary, often 30 to 70% of uploaded records (vendor reports)
- Subject to GDPR and CCPA consent and opt-out rules
The story
What it is
A scrambled email that ad platforms treat as your name tag.
For you
You type your email and press submit. The site may turn it into a code and share it with ad partners. You do not see it, and the same code follows you from site to site.
For makers
Hashing the same email gives the same value everywhere, so platforms can match one person across companies. It replaces cookies as the main ID. The FTC says it is not anonymous, so makers face legal risk if they call it so.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A store sends a scrambled email to Meta, Google and TikTok to find you on each, and to show you the right ads. | Meta, Google Ads, TikTok |
| analytics | A company joins its web, app and store data by one hashed email to see one customer. | LiveRamp, Segment |
| games | A game studio matches a player sign up email to a social account to find lookalike players. | Zynga, Supercell |
| media | A publisher shares logged in readers hashed email with an ad network, to sell targeting without cookies. | The New York Times, Forbes |
| shopping | A retailer matches a purchase to a Facebook account using a hashed email. | Sephora |
| security | A fraud team checks if one scrambled email appears on many accounts. | None named |
Risks
- Same email gives the same code
- Not anonymous in law
What the platform says
- US Federal Trade Commission: No, hashing still doesn't make your data anonymous. The FTC warned that hashing a value like email does not make it anonymous, since the same email gives the same code.
Good uses and abuse
Legitimate uses
- Customer Match audiences
- Offline to online conversion matching
Known abuse
- Cross-site and cross-platform identity linking
- Re-identification by dictionary on known emails
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 5 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
- 2024-07, all: FTC blog: hashing still does not make data anonymous
Related capabilities
Related
- Universal IDs: UID2, ID5, RampID. Can give you a shared ad ID based on your login email, with no cookie
- Conversions APIs (server to server). Can send your purchases and sign ups to ad platforms from the advertiser's server
- Google enhanced conversions. Can match a scrambled email or phone from your checkout to a Google account
Sources
How well checked: Based on official documentation.