Skip to Content
Platform.Ontology

Phone state and numbers

Lets the app see call state, the SIM and the phone's number.

Asks you firstCalls and textsDevice and SIMAndroid and iPhoneWhile you use itWhen the app opensWhen you are signed in

In one line

Can see call state, SIM and carrier info on Android; iPhone shows no number

Lets the app see call state, the SIM and the phone's number.

Reveals carrier, SIM info and in some cases the user's number. Android restricts device IDs such as IMEI to privileged apps since Android 10.

What it can and can't do

What the user does: You tap Allow on the Phone permission prompt

It can

  • Tell whether a call is active
  • See carrier and SIM information
  • See your number on Android with the phone numbers permission

It cannot

  • See the IMEI or serial number on Android 10 and later
  • See your number or IMEI on iPhone
  • Get real carrier names on iPhone 16.4 and later; it shows placeholders

How it differs between platforms: Android gives call state and SIM details after a prompt; iPhone never exposes the number or IMEI.

On Android and iPhone

AndroidiPhone
StatusSupportedPartial
First versionAndroid 6.0 (API 23)iOS 16.4
Permission or entitlementREAD_PHONE_STATE, READ_PHONE_NUMBERS (API 26)none (CTCarrier deprecated)
Protection leveldangerousnone
How access is grantedpromptnone
What the user seesAllow or Don't allownone
How long it lastsUntil revoked or auto-resetn/a
How to take it backSettings > Apps > Permissions > Phonen/a
Store policyPlay: identifiers policy bans persistent IDs from this API for adsApp Review 5.1.1
APITelephonyManager, TelephonyCallback (API 31 needs READ_PHONE_STATE)CTCarrier (deprecated iOS 16), CTTelephonyNetworkInfo
NotesAndroid 10 (API 29) removed non-resettable identifiers (IMEI, serial) for non-privileged apps.iOS never exposes phone number or IMEI; CTCarrier returns placeholder values since iOS 16.4.

Data you get

What comes back: Phone state, carrier, number
Shape: object
How often: event and on demand

FieldTypeUnitRangePrecision
numberstringE.164up to 15 digitsexact

Technical limits

  • No IMEI for ordinary apps on either OS
  • Phone number still exposed on some Android versions with READ_PHONE_NUMBERS
  • Cannot read the number on iOS

The story

What it is

Lets the app see whether you are on a call, plus details about the SIM and the phone's number.

For you

A prompt asks for phone access. If you allow it, the app can tell whether you are on a call and may see your carrier or SIM. The app can pause itself when you get a call.

For makers

Apps like music and games pause during calls. Others use the carrier info to pick a language or a network setting. Older apps abused it to grab device IDs, so it has been trimmed.

Where you see it

TypeExampleApps
musicA music app pauses when a call comes in and resumes after.Spotify
gamesA game pauses a match when you get a call.None named
videoA video call app lowers quality when a cellular call starts.None named
fitnessA run tracker pauses when you take a call.None named
analyticsAn analytics SDK reads the carrier to report network type.None named
securityA fraud tool reads SIM changes to spot a swapped SIM.None named
enterpriseA call center app knows when the agent is on a call.None named

Risks

  • Carrier and SIM details
  • Old device ID tricks
  • Reveals when you are busy

Android and iPhone in short

  • Android: Android 10 removed non resettable IDs like IMEI and serial for apps without privilege.
  • iPhone: iPhone never exposes the number or IMEI. The carrier API has returned placeholder values since iOS 16.4.

Good uses and abuse

Legitimate uses

  • Call handling
  • Carrier-aware apps

Known abuse

  • Persistent device fingerprinting

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bits8Rough identifying entropy, when known

A real example: LinkedIn

Phone Number is on the Apple label (Linked To You, optional on Play). Members enter it for two-step verification and CLEAR identity checks. Android phone state permission was seen in an older build.

History

  • 2017-08, Android 8.0 (API 26): READ_PHONE_NUMBERS split from READ_PHONE_STATE
  • 2019-09, Android 10 (API 29): IMEI, serial and other hardware IDs require privileged permission
  • 2019-09, Android 10 (API 29): Non-resettable device IDs blocked for normal apps
  • 2021-10, Android 12 (API 31): TelephonyCallback requires READ_PHONE_STATE
  • 2023-03, iPhone iOS 16.4: CTCarrier deprecated; returns static placeholder values

Same idea on the web

Sources

How well checked: Based on official documentation.

On this page