Last updated: 10 August 2026
This policy covers AmazHA for Wear OS and Android
(package com.amazha): the watch app and its companion phone app,
which are two halves of one product. It lets you control your own
Home Assistant installation from your watch.
AmazHA for Amazfit / Zepp OS watches is a different product with different capabilities; it has its own privacy policy.
AmazHA has no user accounts, no analytics, no tracking, no advertising, and no developer-operated server that stores anything about you or your home. There is exactly one moment when anything reaches the developer, and you start it yourself: the support form described below.
You enter your Home Assistant address and a long-lived access token in the phone app. They are stored only on your phone, in the app's private storage, and are used to talk to the server you named. They are never sent to the developer or to any third party.
The phone app is the only part that reaches the network. It fetches the state of the devices you chose to show, and sends your taps back to your Home Assistant. That traffic goes directly between your phone and your server — over your own network when your server is local, and over the address you configured when it is remote.
The phone also keeps a local copy of the names of the rooms and devices you enabled, so the settings screens open instantly. It stays on the phone, and you can erase it any time with Preferences → Reset cache.
The watch app stores nothing and never touches the network. It receives what it displays from the phone over the local Bluetooth or Wi-Fi link between your two devices, and it holds that only while it is running. Your access token is never sent to the watch at all.
If you open a camera in the app, the phone fetches a single still image from your Home Assistant and passes it to the watch to display. It is held in memory and written nowhere.
AmazHA for Wear OS reads no health, fitness or body-sensor data of any kind, and requests no health or body-sensor permission. It does not use Health Services or Health Connect. Your heart rate, steps, sleep and every other metric your watch measures are not visible to this app.
Android may include app settings in the backup of your phone, in your own Google Drive, which neither we nor any other app can read. Because those settings include your Home Assistant token, AmazHA tells Android to include them only when that backup can be end-to-end encrypted with your screen lock. If your phone has no screen lock, they are left out.
If you use the support form in the phone app, the name, email and message you type are sent to the developer so we can reply, together with a diagnostic report. The form shows you that report in full before you send it. If you don't use the form, nothing is ever sent.
The report describes your setup, not your home:
Your Home Assistant address, your access token, and your device and room names are never included. Support messages reach the developer through Cloudflare and Telegram, and are kept only as long as needed to answer you.
The optional one-time unlock is an in-app purchase processed by Google Play. Payment is handled entirely by Google; AmazHA never sees or stores your payment details. The app asks Google whether this purchase is owned, and remembers the answer on your phone so the app keeps working offline. Google's own handling of the transaction is covered by the Google Play privacy terms.
AmazHA is a home-automation utility and is not directed at children.
Uninstalling the phone app removes everything the product has stored, including your Home Assistant token — the watch app holds nothing to remove. To have a support message deleted, write to the address below.
If this policy changes, the date at the top changes with it.
Questions about this policy? Use the in-app support form, or email amazha.dev@gmail.com.