Back to Privacy Hub

WebHookDeck: Watch Webhooks Privacy Policy

Last Updated: June 17, 2026

Quick Summary

An Android phone and Wear OS webhook launcher that stores saved HTTP actions, endpoints, request settings, preferences, sync state, tile state, and complication state locally and sends requests only to user-configured endpoints.

App-Specific Details

Specific data handling practices for WebHookDeck: Watch Webhooks.

  • Stores locally: webhook/action names, URLs, HTTP methods, headers, request bodies/templates, favorite actions, import/export state, app preferences, sync state, tile state, and complication state.
  • Uses internet permission so the app can send HTTP requests to endpoints you configure; those requests are not routed through a WebHookDeck developer server.
  • Phone and watch exchange action payloads through Google Play services Wear OS Data Layer APIs so the watch can trigger synced actions.
  • Uses vibration permission on Wear OS for action feedback on supported watches.
  • The developer does not operate a WebHookDeck backend and does not receive your webhook URLs, authorization values, headers, bodies, response data, or run history from normal app use.
  • No ads, analytics SDK, account system, billing dependency, custom backend, location, microphone, camera, contacts, calendar, files/photos, health/body-sensor data, or advertising ID is described by the current code inspected.

Detailed Official Policy

Full technical and legal disclosure for WebHookDeck: Watch Webhooks.

# WebHookDeck Privacy Policy Last updated: June 15, 2026 WebHookDeck is an Android phone and Wear OS webhook launcher published by Quazmoz / Quinn Favo. ## Summary WebHookDeck lets you create, edit, test, sync, and trigger saved HTTP actions. The Android phone app is used for setup and management, while the Wear OS app can trigger synced favorites from the watch app, Tile, or complication. The developer does not operate a WebHookDeck backend service and does not collect, receive, sell, or share your WebHookDeck app data from normal app use. ## Data stored locally WebHookDeck may store action names, endpoint URLs, HTTP methods, headers, request bodies, templates, favorite status, local test or run status, import/export state, preferences, phone/watch sync state, Tile state, and complication state locally on your phone and/or watch. This data is used only to operate WebHookDeck features. Endpoint URLs, headers, request bodies, authorization values, and endpoint responses can be sensitive. Only configure endpoints you own or trust. ## Network access and configured endpoints WebHookDeck requests internet access so it can send HTTP requests to endpoints you configure. When you test or trigger an action, WebHookDeck sends the configured request directly from your phone or watch to that endpoint. Requests are not routed through a WebHookDeck developer server. The endpoint provider you configure may receive and process request metadata, headers, body content, source IP address, and response information according to that provider's own policies. ## Phone and watch sync The Android phone app and Wear OS app may exchange saved action payloads through Google Play services Wear OS Data Layer APIs. This is device-to-device app sync for WebHookDeck functionality, not developer collection and not advertising or analytics sharing. ## Tile, complication, and haptics WebHookDeck includes a Wear OS favorites Tile and a watch face complication. These surfaces use local/synced WebHookDeck app data and do not transmit data to the developer. The Wear OS app may use vibration for action feedback on supported watches. ## Data collection and sharing The developer does not collect, receive, sell, or share WebHookDeck app data from normal app use. WebHookDeck does not include ads, advertising SDKs, analytics SDKs, account registration, Google Play Billing, a developer backend, or custom cloud sync 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. ## Data deletion You can delete local WebHookDeck data by deleting actions where available, clearing app storage in Android/Wear OS settings, or uninstalling the app from your phone and watch. Because WebHookDeck has no developer backend account system, there is no WebHookDeck server-side account data to delete. ## Contact For privacy questions or support, contact quazmoz@vivaldi.net. Public policy URL: https://consultant.quinnfavo.com/privacy/webhookdeck

General Privacy Terms

These terms apply across all our applications.

Questions or privacy requests? Contact us at Quazmoz@vivaldi.net