Privacy Policy
Omarchy AI Usage (Wear OS app), Omarchy AI Usage Watchface, and the Omarchy AI Watch Bridge desktop plugin.
Who this is from
Dmytro Gladkyi, an individual developer, is responsible for these apps. Contact: gladimdim@gmail.com.
What data is collected
None. No personal data, no usage analytics, no crash reporting, no advertising identifiers, no device identifiers. There is no account to create and nothing to log in to. No third-party analytics, advertising or tracking SDK is bundled in any of these apps.
How the apps work
The Wear OS app talks to the Omarchy AI Watch Bridge, an open-source program you install and run yourself on your own computer. Both must be on the same local Wi-Fi network. Communication is direct, on your network only. The developer operates no server and receives no data of any kind.
What travels over that local connection, in both directions:
- From your computer to your watch: AI usage figures the bridge reads from your own machine — quota percentages, reset times, token and session counts for AI coding tools you have installed, and the computer's hostname so you can tell your machines apart.
- From your watch to your computer: the watch's model name and battery percentage, so the desktop widget can show whether the watch is connected, and which quotas you have assigned to which gauge.
- A pairing token generated on your computer when you first connect a watch, so a stranger on the same network cannot read your figures.
All of it stays between those two devices. None of it reaches the developer or any third party.
Finding your computer on the network
To connect without asking you to type an IP address, the watch app looks for the bridge on the local network in two ways: an mDNS/Bonjour lookup, and by asking each address on your own Wi-Fi subnet whether it is running the bridge. That check sends a single request to one address, reads only the reply that identifies the bridge, and keeps nothing about any other device. No inventory of your network is built, stored or transmitted. This happens only while you are connecting a watch, or when a previously paired computer has changed address.
Where data is stored
On your watch, in the app's own private storage: the paired computer's address and name, the pairing token, your gauge choices and alert preferences, and a cached copy of the last figures received so the watch face still shows something when the computer is asleep. On your computer, in files under your own home directory. Nothing is stored anywhere else.
Because the Wear OS app allows Android system backup, this local data may be included in your device's own Google backup if you have that enabled. That backup is between you and Google under Google's privacy policy; the developer has no access to it.
Deleting your data
Tap Unlink this laptop in the watch app to erase the pairing token
and every cached figure from the watch. Uninstalling the app removes all of it
regardless. On your computer, deleting
~/.local/state/omarchy/wearos/ removes the pairing state, and
uninstalling the plugin removes the rest. There is no server-side copy to
request the deletion of, because there is no server.
Permissions, and why each is needed
| Permission | Why |
|---|---|
INTERNET | To reach the bridge on your local network. No internet host is contacted. |
ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE | To tell you when the watch has dropped off Wi-Fi, which is the usual reason a sync fails. |
CHANGE_WIFI_MULTICAST_STATE | For the mDNS lookup that finds your computer. |
POST_NOTIFICATIONS | To alert you when a quota resets or runs out. |
VIBRATE | To buzz your wrist with that alert. |
WAKE_LOCK | Used by the scheduler that refreshes figures in the background. |
No location, camera, microphone, contacts, health, or storage permission is requested, and none of that data is accessed.
Children
These apps are developer tools, are not directed at children, and collect no data from anyone, including children under 13.
Third parties
No data is sold, shared or transferred to anyone. The apps contain no advertising and no third-party analytics. Distribution through Google Play means Google collects install and crash data under its own policy; the developer receives only anonymous aggregate figures from the Play Console and can identify no individual from them.
Security
Connections are protected by a token issued when you pair, and the bridge rejects requests that do not carry it. Traffic runs over plain HTTP because it never leaves your local network and a self-hosted service on a home network has no certificate a device could verify. The content is quota percentages and reset times. Treat your local network as you would for any other device on it.
Open source
Everything described here is verifiable. Both halves are MIT licensed: the Wear OS app and watch face and the desktop bridge.
Changes
If this policy changes, the updated version appears on this page with a new date above. Material changes will also be noted in the app's Play Store release notes.
Contact
Questions about privacy, or this policy: gladimdim@gmail.com, or open an issue on either repository above.