SMS, calendar and call log
A site cannot send or read SMS, read the calendar, or see call history.
In one line
Can't send or see your text messages, calendar or call history from a website
A site cannot send or read SMS, read the calendar, or see call history.
sms: and tel: links only open the user's own app. Calendars arrive as .ics downloads or OAuth sign in.
What it can and can't do
What the user does: You tap an sms: link, tel: link, or a calendar file or sign in button
It can
- Open your own messaging or phone app with a number or message filled in
- Offer an .ics calendar file for you to open
- Connect to your calendar if you sign in with an approved account
It cannot
- Send a text message by itself
- See your text messages
- See your calendar without a sign in you approve
- See your call history
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Not supported | Not available | No such API |
| Edge | Not supported | Not available | No such API |
| Firefox | Not supported | Not available | No such API |
| Safari | Not supported | Not available | No such API |
| Safari on iPhone | Not supported | Not available | No such API |
| Chrome on Android | Not supported | Not available | No such API |
| Samsung Internet | Not supported | Not available | No such API |
How a site asks for it
| API | (none); closest proxy: <a href='sms:...'>, Contact Picker, downloaded .ics |
| How access is granted | not-exposed |
| What the user sees | Not available |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: A site cannot send or read SMS, read the calendar, or see call history.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
none | none | None | Not listed | Not listed |
Technical limits
- No SMS send or read
- No call log
- No calendar read
- Phone number not given
The story
What it is
A website cannot send or read your texts, read your calendar or see your call history.
For you
A site cannot read your messages, calendar or calls. If it needs a contact, you pick one yourself. It is a wall that protects your private data.
For makers
Makers who want these features must ask you to share them one at a time, use a link or an email, or build a native app. This blocks mass data grabs. They rely on forms and sharing instead.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A web chat wanted to read your texts to find friends. It asks you to pick contacts or import a file instead. | None named |
| productivity | A scheduling site wanted to read your calendar. It uses a link you paste or a calendar sign in that you approve. | Calendly |
| social | A social site wanted your call history to suggest friends. It asks you to pick contacts one by one. | None named |
| security | A site wanted to read SMS login codes. It uses a one time code API that reads one code with your approval. | None named |
| shopping | A store wanted to send an order text from your phone. It sends texts from its server instead. | None named |
| health | A health site wanted calendar entries to book a visit. It offers a file you add to your calendar. | None named |
| travel | A travel site wanted to put the trip on your calendar. It offers a calendar file to download. | None named |
Risks
- Blocked by design
- Native apps differ
What the platform says
- MDN Web Docs: Contact Picker API. The closest tool: you pick contacts to share one at a time, and the site sees only your pick.
Good uses and abuse
Legitimate uses
- None by design
Known abuse
- Phishing that invites app installs
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 1 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
- 2016, Chrome: Web SMS API was abandoned
Sources
How well checked: Based on official documentation.