Skip to Content
Platform.Ontology

Own phone number

Android gives it behind a runtime permission; iOS has no API.

Blocked for appsCalls and textsHardware IDsAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can't get the phone's own number on iPhone; Android allows it behind a restricted permission

Android gives it behind a runtime permission; iOS has no API.

The number is a strong identity key, so iOS never exposes it and Android gates it behind a restricted permission set.

What it can and can't do

What the user does: You type your number, or verify it with a text code or Sign in with Apple

It can

  • Ask you to type your number
  • Check it with a text code or Sign in with Apple
  • Get it on Android with the phone numbers permission if the carrier stores it

It cannot

  • Get the number on iPhone
  • Get it on Android without the permission prompt
  • Get it when the carrier does not store it on the SIM

How it differs between platforms: Android gives it behind a permission; iPhone offers no way to get it.

On Android and iPhone

AndroidiPhone
StatusNot supportedNot supported
First versionAndroid 1.0 (API 1)Not available
Permission or entitlementREAD_PHONE_NUMBERS (API 26) or READ_PHONE_STATEnone
Protection leveldangerousnot-exposed
How access is grantednot-exposednot-exposed
What the user seesNot listedNot listed
How long it lastsUntil revokedNot listed
How to take it backSettings > Apps > PermissionsNot listed
Store policyPlay: restricted permission declarationNone listed
APITelephonyManager.getLine1Number()No public API
NotesMay return empty if the carrier does not store itApps must ask the person or verify by SMS or Sign in with Apple

Data you get

What comes back: Phone number
Shape: string
How often: N/A

No individual data fields. The signal is the access itself.

Technical limits

  • iOS: not available at all

The story

What it is

The phone's own number is hidden. Android sometimes shares it behind a prompt, iPhone never does.

For you

An app that wants your number has to ask you to type it, or text you a code. You are rarely asked to hand it over from the phone itself. That keeps your number out of the wrong hands.

For makers

A phone number is a strong identity key and links accounts across the web. Apps wanted it for sign up and fraud checks. Platforms stopped giving it out silently, so apps verify by text or by Sign in with Apple.

Where you see it

TypeExampleApps
messagingA chat app wanted your number to find friends and now texts you a code.WhatsApp, Signal
securityA bank wanted to match your number against its records and asks you to verify.None named
socialA social app wanted your number to link to the address book and asks first.None named
rideshareA rideshare app wanted your number to call the driver and uses an anonymous line.Uber
deliveryA food app wanted your number for the courier and masks it.None named
adsAn ad network wanted a number to track you and cannot read it.None named
paymentsA payment app uses the number as a login and checks it by text.None named

Risks

  • Phone numbers link accounts
  • SMS codes can be intercepted
  • Empty or wrong values

Android and iPhone in short

  • Android: Android may return the number behind a runtime permission, but it can be empty if the carrier does not store it.
  • iPhone: iPhone has no API for the number. Apps must ask the person, verify by SMS, or use Sign in with Apple.

Good uses and abuse

Legitimate uses

  • Auto-fill verification

Known abuse

  • Contact graph keys

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2017-08, Android 8.0 (API 26): READ_PHONE_NUMBERS split from READ_PHONE_STATE

Sources

How well checked: Based on official documentation.

On this page