Nearby Bluetooth devices
Sites cannot scan for nearby Bluetooth devices without a picker you approve.
In one line
Can't scan for nearby Bluetooth devices without a picker you approve
Sites cannot scan for nearby Bluetooth devices without a picker you approve.
Web Bluetooth (Chromium) requires a user gesture, a chooser prompt and a service filter; the page only gets devices the person picks. Silent scanning does not exist. Safari and Firefox do not support Web Bluetooth.
What it can and can't do
What the user does: You tap Connect device and pick one from the browser list
It can
- Ask to connect to one device in Chrome or Edge on Android and desktop
- Show a list for you to choose from
- Work with the one device you pick, for that visit
It cannot
- Scan nearby devices quietly
- See the list of devices you did not pick
- Work in Safari, Firefox, or on iPhone
- Keep a device linked forever without asking again
How it differs between platforms: Web Bluetooth works in Chromium browsers only. Safari and Firefox do not offer it.
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Not supported | Not available | None |
| Edge | Not supported | Not available | None |
| Firefox | Not supported | Not available | None |
| Safari | Not supported | Not available | None |
| Safari on iPhone | Not supported | Not available | None |
| Chrome on Android | Not supported | Not available | None |
| Samsung Internet | Not supported | Not available | None |
How a site asks for it
| API | navigator.bluetooth.requestDevice() (prompt, gesture) |
| How access is granted | not-exposed |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | not applicable |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: none
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
proxy: requestDevice filters | string | None | page sees only the chosen device | Not listed |
proxy: getDevices() | string | None | previously granted devices only | Not listed |
Technical limits
- Presence tracking via beacons
The story
What it is
Sites cannot scan for Bluetooth devices around you without a picker you approve.
For you
A site cannot quietly list your earbuds, watch or other gadgets. If it wants to connect, Chrome shows a chooser and you pick one device. Safari does not offer it at all.
For makers
Apps wanted to scan for nearby devices to find shoppers in stores, to track people or to set up gadgets. The web allows only a user-chosen device, so these uses are blocked. Real gadget setup uses the picker.
Where you see it
| Type | Example | Apps |
|---|---|---|
| smart-home | A smart light site wants to find every bulb nearby, but must wait for you to pick one in the chooser. | None named |
| fitness | A heart rate chest strap page wants to connect, and you choose your strap in the picker. | None named |
| developer | A device maker's setup page uses the picker to flash firmware onto one device. | Espruino |
| shopping | A store app wanted to detect shoppers by phone signals, which a web page cannot do. | None named |
| games | A browser game wanted to find nearby friends' phones, but can only use the picker or a code. | None named |
| security | A tracker wanted to log which Bluetooth gadgets you carry to recognise you, which is blocked. | None named |
| health | A blood sugar monitor page connects to the one sensor you pick. | None named |
Risks
- Needs your clear choice
- Picker can still be tapped by mistake
What the platform says
- Google: Web Bluetooth. Chrome describes a way to talk to a nearby Bluetooth device after you choose it from a list.
Good uses and abuse
Legitimate uses
- None: the browser deliberately withholds it
Known abuse
- Beacon based indoor tracking in native apps
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 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 | 0 | Rough identifying entropy, when known |
Sources
How well checked: Based on official documentation.