Browser extension privacy policy

Last updated: 4 August 2026.

The ShareToWebhook browser extension lets you send the current browser page to webhook endpoints you configure. This policy covers the extension specifically; the general privacy policy covers the website, mobile apps, and support channels.

Data the extension handles

• Current page URL and title, only when you choose to send the current page.
• Optional note text you enter before sending.
• Webhook endpoint names, URLs, and optional custom headers you configure.
• Send history, including endpoint name, timestamp, payload preview, response status, response body, and error message.
• Extension install ID used to connect the browser install to ShareToWebhook account and purchase flows.
• Extension access token returned after license redemption or mobile purchase linking.
• Cached entitlement status, such as whether Pro is active.
• Email address entered for checkout, sent to the ShareToWebhook API to start checkout.
• License key entered for redemption, sent to the ShareToWebhook API and not stored as the ongoing credential.
• Encrypted webhook transfer payloads used when moving webhook configuration between devices.

How data is used

• Page URL, title, optional note, endpoint headers, and endpoint URL are used to send the webhook payload you request.
• Webhook configuration and send history are stored locally in browser extension storage so the extension can operate across sessions.
• Account, license, checkout, mobile-link, entitlement, and transfer requests are sent to https://app.sharetowebhook.com.
• Webhook payloads are sent directly from the extension to the endpoint origins you configure and approve in the browser.
• Encrypted transfer payloads are used only to move webhook configuration between your devices.

Data storage and retention

Webhook configuration, send history, install ID, extension token, user UUID, and cached entitlement status are stored in browser extension local storage. They remain until you remove them by editing or deleting endpoints, clearing extension data, or uninstalling the extension.

Raw license keys are exchanged for an extension token and are not retained as the ongoing credential.

Data sharing

ShareToWebhook does not sell extension data. Data is sent only to:

• The ShareToWebhook API for account, checkout, entitlement, license, mobile-link, and encrypted transfer features.
• Webhook endpoints you configure and authorize.

Permissions

The extension asks the browser for permission only for webhook origins you add or send to, plus the ShareToWebhook API origin. It reads the current tab's URL and title only after you open the popup to share the page.

Remote code

The extension does not load or execute remotely hosted code. Executable extension code is packaged with the extension.

Contact

For privacy questions, email [email protected] or use the contact form.