Read and receive SMS
Lets the app read stored texts and get a copy of incoming SMS.
In one line
Can see texts on Android only if Google approves the app, and never on iPhone
Lets the app read stored texts and get a copy of incoming SMS.
Texts contain bank codes, medical reminders and private chats. Google Play restricts SMS access to default handlers, and Android 17 delays OTP texts.
What it can and can't do
What the user does: You tap Allow when your messaging app asks to access SMS
It can
- List stored texts
- Get a copy of each incoming SMS
- Fill one time codes through the SMS Retriever or User Consent flow, with no permission (Android)
- Fill codes through keyboard AutoFill (iPhone)
It cannot
- See texts on iPhone
- Be on Google Play unless it is a default SMS handler
- See one time code texts right away on Android 17; they are delayed
How it differs between platforms: Android gives text access to approved apps; iPhone gives no SMS access and fills codes through the keyboard.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Behind a flag | Not supported |
| First version | Android 6.0 (API 23) | Not available |
| Permission or entitlement | READ_SMS, RECEIVE_SMS, RECEIVE_MMS, RECEIVE_WAP_PUSH | Not listed |
| Protection level | dangerous | none |
| How access is granted | prompt | not-exposed |
| What the user sees | Allow or Don't allow | none |
| How long it lasts | Until revoked or auto-reset | none |
| How to take it back | Settings > Apps > Permissions > SMS | Not listed |
| Store policy | Play: default SMS handler only unless an exception applies (2019 policy) | App Review 5.1.1 |
| API | Telephony.Sms, SmsRetriever, SMS User Consent API | UITextContentType.oneTimeCode, MFMessageComposeViewController, ILMessageFilterExtension |
| Notes | SMS Retriever and User Consent APIs need no permission. | iOS gives apps no SMS read API; OTP AutoFill fills codes via keyboard QuickType; message filter extensions only sort unknown senders. |
Data you get
What comes back: SMS messages
Shape: list
How often: event on arrival and on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
message | string | chars | up to 160 per segment | exact |
Technical limits
- Default SMS app and companion apps are exempt from OTP delay
- iOS blocks reads entirely
The story
What it is
Lets the app read stored texts and get a copy of new incoming SMS.
For you
A prompt asks to access your texts. If you agree, the app can read bank codes, delivery notices and private chats. Most apps no longer need this, since codes can be filled in another way.
For makers
SMS apps and backups need it. It also used to power code reading for sign in. Google Play limits it to messaging apps because texts hold secrets and malware loves them.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A texting app shows all your conversations and receives new ones. | Google Messages |
| security | A banking trojan reads a login code from a text and moves money, which is why it is restricted. | None named |
| productivity | A backup app saves all texts before a phone move. | None named |
| shopping | A delivery app reads a tracking text to update your parcel. | None named |
| enterprise | A compliance app archives work texts. | None named |
| payments | An app reads a bank text to log spending, which is now blocked in most stores. | None named |
| analytics | A budgeting app wanted to scrape transactions from SMS. | None named |
Risks
- Bank codes stolen
- Private messages exposed
- Malware abuse
Android and iPhone in short
- Android: The SMS Retriever and user consent tools let apps read one code without the permission.
- iPhone: iPhone gives apps no way to read texts. One time codes appear above the keyboard, and message filters only sort unknown senders.
What the platform says
- Google: SMS Retriever. A way for apps to read a one time code from a text without asking for SMS permission.
Good uses and abuse
Legitimate uses
- Messaging apps
- SMS backup
Known abuse
- OTP theft and fraud malware
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2019-03, Android Play policy: Google Play restricted SMS and call log permissions to default handlers
- 2026-06, Android 17 (API 37): OTP protection: standard OTP SMS held for 3 hours from non-default apps for apps targeting 37; WebOTP and SMS Retriever format messages delayed 3 hours for all apps
Related capabilities
Related
- Send SMS. Can send texts on Android once allowed; on iPhone you tap Send yourself
- Call log. Can see your call history on Android, only for apps Google approves
Same idea on the web
- WebOTP (one time code from SMS). Can see one text message code meant for that site, after you allow it
- Call log, SMS and messages. Can't see your calls, texts, or messages from a web page
Sources
- Android 17 release notes
- Google Play: Use of SMS or Call Log permission groups
- Apple: Autofilling one-time codes
How well checked: Based on official documentation.