Skip to Content
Platform.Ontology

Call log, SMS and messages

Web pages cannot read calls, texts or messages on the device.

Blocked for appsDevice detailsIdentityWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your calls, texts, or messages from a web page

Web pages cannot read calls, texts or messages on the device.

No browser API exposes call history or SMS inboxes. WebOTP reads a single matching code. Android native apps need READ_SMS and READ_CALL_LOG; Google Play restricts both heavily.

What it can and can't do

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

It can

  • Take one matching one time code from a text on Android (WebOTP)
  • Fill a code you type in yourself
  • Ask you to paste a code

It cannot

  • See your call history
  • See your text inbox
  • Browse your messages
  • Get around store rules; Google Play restricts SMS and call log access for apps

How it differs between platforms: Android apps can ask for SMS and call log access, but Google Play limits it. Web pages cannot.

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: WebOTPstringNonesingle code from a matching SMS, only if SMS names the site originNot listed

Technical limits

  • Message privacy

The story

What it is

Web pages cannot read your calls, texts or messages.

For you

A website cannot see who you called or what people texted you. If you sign in with a texted code, the browser may offer to fill that one code after you approve it.

For makers

Apps wanted message access to read codes, spot scams and learn about contacts. On the web there is no such access, only one narrow route for verification codes. Native apps need special permissions that app stores restrict.

Where you see it

TypeExampleApps
bankingA bank login wanted to read the texted code on its own. It now relies on the single code filled in after you tap.None named
paymentsA payment page wanted to confirm a code by scanning messages and uses the one time code route.None named
socialA chat site wanted to find friends from your call log and asks you to share contacts through a picker.None named
shoppingA delivery site wanted to read your texts for tracking links and uses its own notifications.None named
securityA scammer page wanted to see your messages, which is why web pages have no such route.None named
messagingA web messaging app wanted to show your texts and only works with its own chats.WhatsApp Web
adsAn advertiser wanted your call frequency as a signal of lifestyle, which is not available.None named

Risks

  • Only a single code can be read
  • Native apps get far more access

What the platform says

  • Google: WebOTP API. Chrome describes a way to receive one verification code by SMS after you approve it.

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