Privacy

What WearDash knows about you

Short version: no account, no tracking, and no way for us to read your configuration or your tokens. This page says exactly what the app and this site do with data.

Last updated: August 2026

No account, no profile

WearDash has no sign-up. We do not ask for your name, email or phone number, and we do not build a profile. Nothing identifies you to us beyond the technical minimum needed to serve a web page.

Pairing between the watch and the editor

The watch shows a one-time code. Both sides derive an encryption key from that code, and everything they exchange is encrypted end to end. Our relay only ever holds opaque encrypted blocks, in memory, for the duration of the session; nothing is written to a database or a log, and a block is deleted once read.

Tokens and certificates

Tokens, passwords and client certificates are typed in the editor, encrypted in your browser, and stored on the watch in encrypted storage. They never appear in the configuration file, and we cannot read them, even in transit.

Your dashboards talk to your servers

The watch sends its requests directly to the addresses you configure, such as your Home Assistant instance or your own API. That traffic never passes through us, so we have no visibility on what you control or when.

Microphone

The microphone is used only when you press a voice control, and the recording goes to the destination you configured: your Android TV for a voice search, or the endpoint written in your action. We never receive audio and none is stored on the watch after it is sent.

Purchase

Premium is a one-time purchase handled by Google Play. Payment is between you and Google; we receive no card data. The app asks Play whether this device owns the purchase and remembers the answer locally.

This website

No analytics, no advertising, no third-party cookies. One cookie is set if you switch the language, so the site remembers your choice. The server keeps standard access logs, kept short and used only to keep the service running and to block abuse.

Self-hosting

If you run the open-source pairing front yourself, none of the above involves us at all: the relay runs on your server, in memory, and your watch never contacts weardash.app.

Your data, your devices

Since we hold no account and no configuration, there is nothing on our side to export or delete. On the watch, Settings lets you erase all stored secrets, and uninstalling the app removes everything it holds.

Questions about this page: contact@weardash.app