Skip to Content
Platform.Ontology

Serial number, IMEI and device ID

Sites cannot read your serial number, IMEI or advertising ID.

Blocked for appsDevice detailsHardware IDsWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your serial number, IMEI, or advertising ID from a web page

Sites cannot read your serial number, IMEI or advertising ID.

No unprompted API exposes hardware identifiers. Managed ChromeOS and enterprise policies expose serial to allowlisted extensions only (chrome.enterprise.deviceAttributes). A regular site gets none; fingerprints are rebuilt from many signals instead.

What it can and can't do

What the user does: Nothing. Pages have no way to ask for this

It can

  • Build a tracking guess from many small signals
  • Set its own cookie or ID that stays on your browser
  • Let managed work devices pass a serial to approved extensions

It cannot

  • See your hardware serial
  • See your IMEI or phone ID
  • See your advertising ID
  • Get an ID that survives clearing site data on its own

Browser support

BrowserStatusFirst versionNote
ChromeNot supportedNot availableNone
EdgeNot supportedNot availableNone
FirefoxNot supportedNot availableNone
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot availableNone
Samsung InternetNot supportedNot availableNone

How a site asks for it

APInone
How access is grantednot-exposed
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnot applicable
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: none
How often: static per session

FieldTypeUnitRangePrecision
proxy: fingerprint hashstringNonecombine UA, screen, fonts, GPU for an approximate IDNot listed
proxy: Web Bluetooth or WebUSB serialNumberstringNoneonly for a device the user picked in a promptNot listed
proxy: enterprise deviceAttributesstringNonemanaged Chrome extension policy onlyNot listed

Technical limits

  • Hardware ID is permanent

The story

What it is

Sites cannot read your serial number, IMEI or advertising ID.

For you

A web page cannot see your device's serial number or phone ID. That is a big reason the web is safer to browse than many apps. Only company managed devices can reveal some of it to approved tools.

For makers

Hardware IDs are the strongest way to follow a person for ads and fraud checks. The web gives no such ID, so sites use cookies, logins and fingerprints. Managed work devices can expose a serial to approved tools only.

Where you see it

TypeExampleApps
adsAn ad network wanted the advertising ID and instead uses cookies or fingerprinting.None named
securityA fraud team wanted the serial to spot repeat abuse and builds a device profile instead.FingerprintJS
enterpriseAn IT portal wanted laptop serials and needs a managed extension.None named
bankingA bank wanted a permanent device ID and uses a stored device token after a login.None named
gamesA game site wanted to ban cheaters by device and bans accounts and IP ranges instead.None named
analyticsAn analytics team wanted a stable ID and settles for first party IDs.Google Analytics
shoppingA retailer wanted to match a phone to a past visit and relies on login.None named

Risks

  • Fingerprints partly fill the gap
  • Managed devices can expose a serial

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Sites attempt proxies to recover it

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bits0Rough identifying entropy, when known
  • MAC address. Can't see your device's network hardware address (MAC)

Sources

How well checked: Based on official documentation.

On this page