Privacy policy
Effective 16 November 2026
Contact: support@homeband.app
Homeband plays the sound from one of your devices on your other devices, over your own network. This policy says what the app does with your information, for the Android and Linux versions.
The short version
- No account. There's no sign-up or sign-in.
- No server. Your sound goes straight from one of your devices to another, encrypted. There is no Homeband server for it to pass through, and we never receive it.
- No tracking of our own. The app has no analytics and no advertising, and we receive nothing from it.
- No recording. The app doesn't save the audio it sends or plays.
- Two things involve Google, both on Android: the QR code scanner and purchases. They're explained below.
- The website counts visits, without cookies. It also uses Google Analytics and Microsoft Clarity: in Europe only if you allow them, elsewhere unless you turn them off. See This website.
We don't sell or share your information, because we don't have any of it.
What travels over your network
Your sound. It goes only to speakers you have paired and switched on. Each packet is encrypted and authenticated (ChaCha20-Poly1305), under a key made for that stream and delivered over the encrypted link below. A device on your network that isn't paired can't listen in, and a speaker refuses audio it can't authenticate.
The link between paired devices. A source and a speaker keep an encrypted connection (QUIC with TLS 1.3) for pairing, starting and stopping, and status. Paired devices tell each other their names, app version, operating system, latency, buffer levels and counts of lost packets, and a speaker tells its source how loud its device's volume is and whether it's muted, so the app can show how each speaker is doing. A device playing to a speaker can change that volume, unless the speaker's owner turns this off in its settings.
What others on your network can see:
- While a device is being a speaker, it announces itself over mDNS, unencrypted, so sources can find it. Anyone on the same network can read this: its IP address, the name you gave it, a stable id, the protocol version and its ports. So choose a name you're happy for others on that network to see. On first run the app suggests the name the device already has, which you can change: on Android the device name from its settings, the one Bluetooth also shows, and on Linux the computer's hostname. With no name set, a phone uses that device name or, failing that, its model. The id is a fingerprint of the device's public key. In the rare case that the Android Keystore isn't available, it's Android's device id for this app instead.
- A device that connects to a speaker learns the speaker's name, app version and operating system before pairing, over an encrypted connection.
- A speaker's QR code contains its IP address, name, public key and a one-time pairing code. Anyone who can see your screen can read it.
None of this reaches us.
What leaves your network
The app's own engine opens no connection to the internet. To find which local address to use, it asks the operating system which network interface would reach a public address, and that sends nothing. Two things on Android involve Google.
1. The QR code scanner. Scanning a code uses Google's ML Kit, which is built into the Android app. Camera images are processed on the device, and the app doesn't save or send them. Google's documentation says ML Kit collects device information, app information, device or other identifiers, performance metrics, API configuration, input and output size, feature version, event type and error codes, for diagnostics and usage analytics. It says this travels over HTTPS and isn't transferred to third parties. We don't receive any of it. We haven't measured when it's sent, so we can't promise that avoiding the scanner avoids all of it. You can pair without the scanner, by tapping a device in the list or typing its address. The Linux version has no scanner.
2. Google Play. Where Homeband Pro is offered, the app asks Google Play for its price and whether you own it, and Google handles the purchase. We never see your payment details. Google's own terms and privacy policy apply. The app keeps a small file on the device recording that you own Pro, so it keeps working offline. Separately, if you tap Rate it, the Play Store opens.
Device backup. The app opts out of Android's device backup and device-to-device transfer, so the files listed below aren't copied anywhere.
Linux. No Google components are involved. The app doesn't check for updates by itself. If you run AppImageUpdate, that tool downloads from the project's GitHub releases.
If you email us, we receive your email and whatever you put in it, and use it only to answer you.
What's kept on your device
| What | Why |
|---|---|
| Settings: the device's name, what it's for, quality, delay, channels, and whether to start listening when opened | So it works the same next time |
| How long this device has played in total, how many streams, and whether it has asked you for a review | To show you your total, and to ask at most once. Counted on this device only |
| The public keys of devices you've paired with | So they connect with no prompt, and a device that changes its key gets noticed |
| Paired speakers: names, last IP address, ports, and whether each is switched on | So they appear, and connect, before anything else has found them |
| Names you've given to outputs and speakers | So your names stick |
| This device's private key | It's how other devices recognize this one. On Android it's sealed with the Android Keystore. On Linux it's in the system keyring, or, if there's no usable keyring, in a file only your user can read |
| A note that you own Pro, where Pro is offered | So Pro works offline |
| The last crash report: the error and where in the code it happened | So it can be offered to support |
| On Linux, a note of your speakers' mute state while the app has muted them | To restore them if the app crashes |
Audio is held in memory only as long as it takes to play or send it, and is never written to storage. The one exception is a developer setting on Linux, an environment variable you'd have to set yourself, that saves it to a file for testing.
Recent log lines are kept in memory and go when the app closes. They contain device names and addresses on your network.
To remove it: forget a speaker from its details screen to remove that pairing. Uninstalling on Android removes the app's files from the phone. Removing the Linux package leaves your files in place, so also delete ~/.local/share/app.homeband.Homeband and the app's entry in your keyring.
Diagnostics
Copy diagnostics, in Settings, copies a report to your clipboard: recent log lines, the last crash, the app version and the device type. It contains device names and addresses on your network, and no audio or keys. The app doesn't send it anywhere. It goes only where you paste it.
Android permissions
| Permission | Why |
|---|---|
Microphone (RECORD_AUDIO) |
Android requires this for an app to capture what the phone is playing. The microphone itself isn't used. Asked for when you first play from the phone |
FOREGROUND_SERVICE_MEDIA_PROJECTION |
Lets that capture run in the background. Android also shows its own screen-capture consent each time you start. Only sound is captured, never the screen. Calls aren't captured |
Notifications (POST_NOTIFICATIONS) |
To show the notification Android requires while the app is playing or listening, and to tell you when another device asks to pair while Homeband is out of sight |
FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PLAYBACK |
To keep playing as a speaker with the screen off |
Nearby devices (NEARBY_WIFI_DEVICES) |
To find speakers on your Wi-Fi and reach them. Declared as not used for location |
ACCESS_LOCAL_NETWORK |
The same need on later Android versions |
Camera (CAMERA) |
Only for scanning a pairing code. Optional: without it you can pair by tapping a device or typing its address |
INTERNET |
Android's permission for any network use, including your own Wi-Fi |
ACCESS_NETWORK_STATE |
To notice the network changing, and reconnect sooner |
ACCESS_WIFI_STATE |
To keep Wi-Fi in its low-latency mode while playing, which avoids dropouts |
CHANGE_WIFI_STATE |
To ask Wi-Fi not to link your phone directly to another device in the group, which some phones try and which can cut the sound. It changes nothing else about your Wi-Fi |
CHANGE_WIFI_MULTICAST_STATE |
So the phone receives the local announcements that speakers make |
WAKE_LOCK |
To keep playing with the screen off |
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS |
To offer a battery exemption for long sessions. Only if you tap Allow |
com.android.vending.BILLING |
Added by the Google Play billing library, for Homeband Pro. Unused where Pro isn't offered |
The app doesn't ask for your location, contacts, files or photos.
This website
This section is about homeband.app, not the app.
Counting visits, for everyone. Cloudflare Web Analytics counts which pages are visited, the site you came from, your browser, device type and country, from what your browser sends with each request. It sets no cookies, doesn't identify you, and doesn't follow you to other sites.
Google Analytics and Microsoft Clarity. Where they run depends on where you are:
- In the EU, the rest of the European Economic Area, the UK and Switzerland, the site asks first. They run only if you choose Allow. If the site can't tell where you are, it asks too.
- Elsewhere they run unless you turn them off.
- If your browser sends Global Privacy Control, they don't run, wherever you are.
When they run:
- Google Analytics 4 measures how the site is used: pages viewed, how visitors arrived, scrolling, and clicks on links.
- Microsoft Clarity records how pages are used (clicks, scrolling and pointer movement, with the page's text masked) so we can see where people get stuck.
Both set cookies on homeband.app and send what they measure to Google and Microsoft, which process it for us. Nothing is used for advertising: both are told that advertising storage isn't allowed. Google Analytics keeps it for 14 months. Clarity keeps recordings for 30 days and its other reports for 13 months.
If you choose No thanks, or turn them off from Cookie choices at the foot of every page, neither loads. Your choice is kept in your browser's storage, not in a cookie, and you can change it at any time. Turning them off clears their cookies. Where you are is worked out, by country only, from Cloudflare's own information about the connection. Your browser keeps it until you close the tab, and it isn't sent anywhere.
Email. If you write to us, including with the Tell me when it's out button, we use your address only to reply and, if you asked, to tell you once when Homeband is out for your devices. We don't add you to a mailing list. Ask, and we'll delete it.
Your rights
We hold no information about you, so there's nothing for us to give you, correct or delete, other than any email you've sent us. For what's on your device, see above. For what Google holds, see Google's privacy policy.
Changes
If this policy changes, we'll update this page and its effective date.
Contact
Homeband is provided by Daviansoft Inc.