Back to Privacy Hub
WristDash: Watch Dashboard Privacy Policy
Last Updated: June 17, 2026
Quick Summary
An Android phone and Wear OS quick-action dashboard that stores user-configured endpoints, dashboard actions, favorites, sync state, tile state, and complication launch state locally while using network access only for user-configured actions.
App-Specific Details
Specific data handling practices for WristDash: Watch Dashboard.
- Stores locally: connection settings, action names, action IDs, favorite actions, sync metadata, tile state, complication launch state, and app preferences.
- Uses internet and network-state permissions so the app can call endpoints you configure and show clearer offline or unreachable-state messages.
- Uses vibration permission for haptic success or failure feedback on supported watches.
- Phone and watch exchange dashboard configuration through Google Play services Wear OS Data Layer APIs.
- The developer does not operate a WristDash backend and does not receive your endpoint URLs, authorization values, dashboard actions, or action results from normal app use.
- No ads, analytics SDK, account system, advertising ID, location, microphone, camera, contacts, calendar, files/photos, health/body-sensor data, or billing dependency is described by the current code inspected.
Detailed Official Policy
Full technical and legal disclosure for WristDash: Watch Dashboard.
# WristDash Privacy Policy
Last updated: June 15, 2026
WristDash is an Android phone and Wear OS quick-action dashboard app published by Quazmoz / Quinn Favo.
## Summary
WristDash is designed around user-configured automation/dashboard actions. Setup is handled by the Android phone companion app, and the Wear OS app can display synced quick actions, a Tile, and a watch face complication.
The developer does not operate a WristDash backend service and does not collect, receive, sell, or share your WristDash app data from normal app use.
## Data stored locally
WristDash may store the following data locally on your phone and/or watch:
- Connection settings, such as an endpoint URL or server address you enter.
- Action names, action IDs, favorite action selections, and dashboard configuration.
- Local app preferences and setup state.
- Phone/watch sync state and last synced dashboard configuration.
- Local Tile state used to show quick actions.
- Local complication state used to launch the app.
This data is used only to operate the configured dashboard and quick-action features.
## Network access and configured endpoints
WristDash requests internet access so it can call the endpoints you configure. It also requests network-state access so the app can distinguish no-network situations from an unreachable configured endpoint.
When you trigger an action, WristDash may send the configured request to your configured server or endpoint. Those requests go to the endpoint you configure; they are not routed through a WristDash developer server.
Endpoint URLs, authorization values, headers, action names, and action payloads can be sensitive. Only configure endpoints you own or trust.
WristDash is an independent app and is not affiliated with Home Assistant, Google, or any third-party automation platform.
## Phone and watch sync
The Android phone app and Wear OS app may exchange dashboard configuration through Google Play services Wear OS Data Layer APIs. This is device-to-device app sync for WristDash functionality, not developer collection and not advertising or analytics sharing.
## Tile, complication, and haptics
WristDash includes a Wear OS Tile for quick actions and a watch face complication for app launch. These surfaces use local/synced WristDash app data and do not transmit dashboard data to the developer.
The app may use vibration for haptic confirmation when an action succeeds or fails on supported watches.
## Data collection and sharing
The developer does not collect, receive, sell, or share WristDash app data from normal app use. WristDash does not include ads, advertising SDKs, analytics SDKs, account registration, a developer backend, custom cloud sync, or in-app purchase code in the current code inspected.
Google Play, Android, Wear OS, and Google Play services may process limited technical data for app distribution, updates, platform security, Wear OS sync, tiles, complications, and device functionality according to their own policies.
Your configured endpoint provider may process data from requests you choose to send through WristDash according to that provider's own policies.
## Data deletion
You can delete local WristDash data by clearing app storage in Android/Wear OS settings or uninstalling the app from your phone and watch. Because WristDash has no developer backend account system, there is no WristDash server-side account data to delete.
## Contact
For privacy questions or support, contact quazmoz@vivaldi.net.
Public policy URL: https://consultant.quinnfavo.com/privacy/wristdash
General Privacy Terms
These terms apply across all our applications.
Questions or privacy requests? Contact us at Quazmoz@vivaldi.net