Skip to Content
Platform.Ontology

Your phone number

A page cannot read the phone number of your phone or SIM.

Blocked for appsDevice detailsIdentityWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your own phone number from a web page

A page cannot read the phone number of your phone or SIM.

No web API returns the device's own number. Proxies: WebOTP reads an SMS code (needs a prompt-free user flow but only the code, only formatted for the origin), Credential Management and Contact Picker give numbers the person chooses.

What it can and can't do

What the user does: You type your number, pick one from a contact picker, or tap Autofill

It can

  • Take a one time code from a text message on Android (WebOTP)
  • Use a number you type in or pick
  • Fill a number from your saved info if you choose it

It cannot

  • See the number of your phone or SIM
  • See your texts beyond one matching code
  • See numbers you did not choose
  • Get the code unless the text matches the site

Browser support

Chromenot offered
Edgenot offered
Firefoxnot offered
Safarinot offered
iPhonenot offered
Androidnot offered
Samsungnot offered
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: WebOTP APIstringNonereads a one-time code in an SMS formatted with @domain, not the numberNot listed
proxy: Contact Picker APIstringNonereturns tel values only after a picker the user confirms (Android Chrome 80)Not listed
proxy: autocomplete=telstringNonefills from saved profile on user actionNot listed

Technical limits

  • PII and SIM swap risk

The story

What it is

A page cannot read the phone number of your phone or SIM.

For you

A site cannot learn your phone number by itself. You type it in, and later it may fill a code that arrives by text. That is all it gets.

For makers

Phone numbers are very sticky IDs, used to link accounts and track people. The web gives no way to read one. Apps ask you to type it, then confirm it with a code.

Where you see it

TypeExampleApps
bankingA bank wanted your number for login and sends a code to the number you type.None named
messagingA chat site wanted to find friends by number and asks you to enter or import it.WhatsApp Web
rideshareA ride site verifies your number with a one time code before booking.None named
deliveryA delivery site texts a code to confirm the number you typed.None named
datingA dating site asks you to verify a number by code instead of reading it.None named
adsAn ad vendor wanted your number to match profiles and gets only hashes you gave.None named
securityA fraud team checks that the number you typed matches the code, not the SIM.None named

Risks

  • Typing it gives it away
  • Codes can be phished

What the platform says

  • Google: WebOTP API. Chrome describes filling a one time SMS code for the site after you approve, without giving the number.

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

Sources

How well checked: Based on official documentation.

On this page