Alexa app information: what the companion application does
The app is usually described as the thing you use to set a speaker up, which undersells it considerably. Setup takes a few minutes once. The app remains the only place several settings exist at all.
Why the app stays relevant
Almost nothing happens inside an Echo. It captures sound, sends it away, and plays back what comes back. What holds everything together is your account — what each unit is called, which room it sits in, the services tied to it, the privacy switches. The app is the window onto it, not a setup wizard that has outlived its purpose.
Four questions to land you on the right screen for your phone. Platform names differ more than you would expect.
Loading…
How the app is organised
This arrangement explains several things people find odd. It is why a replacement speaker inherits your settings the moment it is added. It is why a change made on one device sometimes affects another. And it is why the app remains necessary long after setup — it is the control panel rather than an installer.
It also explains why an account has to exist before a speaker can be useful. The account's country setting, chosen at creation, determines which features and languages are available, and it is not something that can be varied per speaker.
Three things worth opening
The permission paths for each platform, and the reasoning behind them.
iPhone and iPad: Local Network and Bluetooth
- Where the switches live
- Why one may be missing
- What Local Network means
OpenClose
iPhone and iPad: Local Network and Bluetooth
- Where the switches live
- Why one may be missing
- What Local Network means
The two switches worth knowing about, Local Network and Bluetooth, sit under the Alexa entry in the handset’s own settings.
"Local network" means the other things connected to your own Wi-Fi at home, not the internet. This is the switch behind the majority of occasions when an app reports finding nothing.
This allows the short-range link the app uses to reach a speaker that is not yet on any network.
If Local Network is missing from that screen entirely, the app has not requested it yet. It appears the first time the app needs it and you agree — the list on that screen only ever shows permissions an app has actually asked for.
Android: Nearby devices, or Location on older phones
- What changed at Android 12
- The two-part requirement on older phones
- Where to check your version
OpenClose
Android: Nearby devices, or Location on older phones
- What changed at Android 12
- The two-part requirement on older phones
- Where to check your version
Permissions sit under the app’s own entry in the handset’s settings, in the section covering app information.
Android 12 brought in Nearby devices as its own separate permission, covering the discovery of nearby hardware over Bluetooth. Before it existed, this job was done by the Location permission — an arrangement most people found baffling, since the task has nothing to do with maps.
On Android 11 and earlier there is no Nearby devices switch, and Location does the job instead. Two separate things are involved: the app's own Location permission, and the system-wide location service. Granting the app permission while the phone's location service is off is the thing most often overlooked on these releases, because everything looks correctly configured.
The release number is recorded in the handset’s own settings, in the section describing the phone itself.
Why phones withhold this in the first place
- What an app could learn
- Why the reasoning is sound
- The unfortunate side effect
OpenClose
Why phones withhold this in the first place
- What an app could learn
- Why the reasoning is sound
- The unfortunate side effect
It is reasonable to wonder why a phone makes such a production of letting an app look around the house. The reasoning is sound, and knowing it makes the prompts less irritating.
An application that can list everything connected to your home network learns a great deal without asking a single question: how many people live there, what they own, roughly what they can afford, when the house is occupied. One that can scan for Bluetooth devices in range learns more still, and in aggregate across many phones can work out where you are without ever touching the location service.
Both platforms concluded these are capabilities worth asking about individually rather than granting quietly at installation.
The arrangement has one unfortunate consequence, and it accounts for a large share of the confusion around these devices. Where permission has been withheld, nothing tells the app "you lack permission" in a form it can pass on to you. It simply looks, finds nothing, and reports finding nothing.
Three more things worth knowing
Notifications can be turned down without being turned off
The app asks permission to send notifications, covering genuinely useful things — a timer finishing, a message arriving on a household device — and also product announcements and suggestions, which many people find excessive. These are separable, both inside the app's own settings and at the level of the phone's notification settings for that app. Turning off the promotional kind does not affect the functional kind.
The same account works on several phones
Everything lives on the account, so the app can be signed in on several phones and tablets at once, all seeing the same speakers and the same settings. This is worth knowing in households where one person did the setting up — anybody else in the house can sign in to the same account from their own phone and reach the same controls, including the privacy settings, which are considerably easier to review on a screen than to ask about aloud.
The privacy controls are only here
Recording history, the automatic deletion schedule, and the switches governing whether recordings contribute to service development are all in the app's privacy section and nowhere else.
Reading through a week of your own recording history is, if nothing else, the quickest way to learn what sets a speaker off by mistake. It is very often a name, or somebody on the television.
What the app cannot do, and why that is worth knowing
Knowing the edges of a tool saves time otherwise spent looking for settings that do not exist.
It cannot reach a speaker that is not on your network
Once a speaker has joined your Wi-Fi, the app talks to it through the manufacturer's servers rather than directly. That is why you can rename a speaker or set a routine from a phone on mobile data miles away. The corollary is that a speaker which is not on the network is not reachable by the app at all — there is nothing to adjust remotely, because the only path to it runs over the connection in question.
It cannot see what your router is doing
The app knows which network a speaker was given and whether it is currently reachable. It has no view of your router's settings, no knowledge of which band anything is using, and no way to change any of it. Anything concerning bands, channels, security types or device isolation is handled inside the router's configuration pages, opened in a browser, and is entirely separate from the app.
It cannot recover an account
Account matters — signing in, changing details, anything to do with the account itself — are handled by the manufacturer, through the app's own sign-in screens or the manufacturer's own website. No third party has any part in that process, and no third-party website has a legitimate reason to present a sign-in form for it.
What it does hold that nothing else does
Against those limits, it is worth restating what only the app can reach. Every privacy control — the recording history, the automatic deletion schedule, the switches about service development — exists there and nowhere else. So do routines, household membership, and the naming that stops a list of speakers becoming indistinguishable.
A device with no screen has to keep its settings somewhere. For these speakers, that somewhere is a phone.
Common questions about the app and permissions
What the app controls, and the settings it asks for. Each one expands.
What does the app actually do after setup?
It remains the control panel. What each unit is called, which room it belongs to, the routines, the alarms, whichever music services are tied in, and all of the privacy switches live there, because a speaker with no screen has nowhere else to put them.
Everything is held on the account rather than on any individual speaker, which is why a replacement inherits your settings immediately.
Which permissions does the app need?
On an iPhone: Local Network and Bluetooth, both under Settings in the app's own entry. On newer Android: Nearby devices, plus Location. On Android 11 and earlier: Location for the app, and the phone's system-wide location service switched on as well.
These gate local discovery, which is how the app finds a speaker in the first place.
What does a discovery permission control?
It decides whether software is allowed to list the hardware sharing your network and scan over Bluetooth. Both platforms keep it switched off until it is granted, and while it is off the platform does not surface that state in any form the app can display.
An app is only ever describing what it is permitted to see, not what exists.
Why does Android ask for Location?
On Android 11 and earlier, Bluetooth scanning was gated behind the Location permission, on the reasoning that nearby Bluetooth beacons reveal position. Maps do not come into it.
Android 12 introduced Nearby devices as a dedicated permission, though Location is still involved in identifying which Wi-Fi networks are in range.
Where are the privacy settings?
In the app's privacy section, and nowhere else — there is no way to reach them by speaking. That covers recording history, automatic deletion schedules, and the switches governing whether recordings contribute to service development.
Reading a week of your own history is the quickest way to learn what sets a speaker off by mistake.
Check what you have picked up
Three questions, with the reasoning shown after each answer. Nothing is recorded.
Three questions on permissions
0 of 3 correctWhat does a discovery permission control?
It gates local discovery — whether an app may enumerate devices on your network and scan over Bluetooth. Both platforms keep it off until it is granted.
On an iPhone, which switch gates local device discovery?
Local Network, under Settings in the app's own entry. If it is missing from that screen entirely, the app has not requested it yet.
Why does older Android ask for Location to find a speaker?
Because on Android 11 and earlier, Bluetooth scanning sat behind the Location permission — nearby beacons can reveal position. Android 12 introduced Nearby devices to separate the two.
What to read next
If you would rather be pointed straight to it, the search field on this page runs an automated index across everything published on the site. Tap it and it will offer you the relevant guides. It returns links only — there is no person on the other end, and it cannot see your device or your account.