Privacy Policy for Text to Webhook

Summary

This extension enables a user to send selected text or the current tab URL to user-configured webhook endpoints. It stores webhook configuration locally in your browser and does not transmit user data to the developer.

Data the extension stores

The extension stores the following data locally using the browser's storage API (chrome.storage):

• Webhook label (a short text label you provide)
• Webhook URL(s) that you configure
• Optional allowed host permissions (if requested)

No other personal data, browsing history, cookies, or external analytics identifiers are stored by the extension.

What the extension sends

When you use the extension (via right-click menu or popup), it sends the selected text or current tab URL directly to the webhook URL you chose. That transmission goes directly from your browser to the webhook endpoint and is not routed through or stored by the developer's servers.

Because webhook URLs can point to third-party services, please ensure you trust the endpoints you configure. The developer has no access to the data you send to those endpoints unless you explicitly share it.

Notifications and user interactions

• The extension shows brief success or error notifications when webhook requests complete, so you are informed of the result.
• When deleting a webhook, the extension asks for confirmation to prevent accidental removal.

Third-party services

The extension does not include third-party analytics, crash reporting, or advertising. If you configure a webhook that points to a third-party service (for example, webhook.site, n8n, IFTTT, or a custom server), that third party's privacy practices will apply to the data you send to them.

Permissions

The extension requests only the permissions necessary for its functionality:

• storage: to save your webhook configuration locally.
• contextMenus: to add right-click menu items for sending selected text.
• notifications: to show brief success/error messages after webhook requests.
• host permissions (optional): when adding a webhook on a new domain, the extension may request permission to access that host to send requests. Permission requests are prompted in the browser and require your approval.
• tabs: to read the current tab's URL for sending from the popup. The extension does not read or send any other tab data.

Data retention and deletion

Your webhook configuration remains stored locally until you delete it. To remove stored webhooks, open the extension options and delete the entries (with confirmation prompts). Clearing your browser extension data or uninstalling the extension will also remove this local data.

Developer access

The developer does not receive or collect your webhook URLs or the data you send through them. All configuration and transmitted data remain under your control in your browser and at the destination webhook.

Contact

If you have questions about this privacy policy or the extension, contact: Wynand Nel at text-to-webhook@cgtools.co.za.