Whole address book or call log
A site cannot read your whole contact list, call history or SMS.
In one line
Can't see your whole contact list, call history or text messages
A site cannot read your whole contact list, call history or SMS.
The only contact route is the picker, one chosen entry at a time. No web API reads call logs, SMS, voicemail or calendar events.
What it can and can't do
What the user does: Nothing. No browser lets a site do this, even if you tap Allow
It can
- Ask you to pick contacts one at a time, on browsers that offer a contact picker
- Receive only the name, number or email you chose in the picker
It cannot
- Browse your full address book
- See who you called or who called you
- Look at your text messages or voicemail
- See your calendar events
How it differs between platforms: The contact picker exists only in Chrome on Android. Safari, Firefox and desktop browsers have no way to share contacts at all.
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 is navigator.contacts.select() |
| Browser compat keys | api.ContactsManager |
| 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 read your whole contact list, call history or SMS.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
contacts | none | None | no bulk read | Not listed |
Technical limits
- No bulk contact read
- No SMS send or read (sms: links open the user's app only)
- No call log
- No calendar read (only .ics download or a linked calendar via OAuth)
The story
What it is
A website cannot read your full contact list, call history, texts or calendar. The browser blocks it by design.
For you
You never see a prompt for this, because the option does not exist. If a site wants a contact, you pick the person yourself from a list your phone shows, and the site gets only that one entry.
For makers
Makers who want a friends list, a call log or message history cannot get it from a web page. They either build a native app, use a sign in with Google or Microsoft that shares contacts, or ask people to type or upload names.
Where you see it
| Type | Example | Apps |
|---|---|---|
| social | A new social network wants to find your friends on day one. The web version cannot scan your address book, so it asks you to pick a few contacts or import a file. | None named |
| messaging | A web chat app like WhatsApp Web cannot read your phone contacts directly. It syncs them from the phone app instead. | WhatsApp Web |
| shopping | A gift site wants to send a card to a friend. It shows the contact picker so you choose one person and the site never sees the rest. | None named |
| games | A browser party game wants to invite friends. It makes a share link you send yourself, since it cannot read your contacts. | None named |
| productivity | A web email or CRM tool imports contacts through a Google sign in permission, not through the browser itself. | Gmail, HubSpot |
| security | A scammy site that wants to harvest your contacts to spam them is stopped, because the web has no way to read the list silently. | None named |
| rideshare | A web ride booking page wants to share your trip with a friend. It opens your own messaging app with a link instead of reading contacts. | None named |
Risks
- Native apps can ask for much more
- Phishing can still ask you to type contacts
What the platform says
- Google Chrome: Contact Picker API. Lets a site ask for one or a few contacts you choose by hand, instead of your whole address book.
Good uses and abuse
Legitimate uses
- None (by design)
Known abuse
- Apps that want these must be native or use OAuth APIs
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
- 2020, Chrome on Android 80: Picker added; bulk read never offered
Related capabilities
Related
- Contact Picker. Can see only the contacts you pick, and only the details it asks for
Sources
How well checked: Based on official documentation.