Terms of use

Last updated: 26 June 2026.

These terms apply when you visit the ShareToWebhook website, join the mailing list, contact us, or use any preview, beta, app, browser extension, or paid version of ShareToWebhook.

ShareToWebhook is built to help you send content from your device or browser to webhook endpoints you configure. By using it, you agree to use it responsibly and only with systems, accounts, and endpoints you are authorised to connect.

Product status

ShareToWebhook is in early development. Features, platform availability, pricing, limits, payload formats, integrations, and support processes may change before and after public launch.

Preview and beta access may be incomplete, unstable, or withdrawn. We may add, change, pause, or remove preview features while learning what the product needs to become.

Direct webhook delivery

The core ShareToWebhook workflow sends webhook requests directly from your device or browser to the endpoint you configure. ShareToWebhook does not operate a proxy, relay, hosted queue, hosted delivery log, or processing server for those direct-send payloads.

Because delivery depends on your device, browser, network, operating system, endpoint configuration, and destination provider, ShareToWebhook cannot guarantee that a webhook will be delivered, delivered once, delivered in order, accepted by the destination, processed correctly, or preserved if something fails.

You are responsible for testing your configured endpoints, monitoring downstream automations, handling retries or duplicate requests where needed, and deciding whether a workflow is suitable for important or time-sensitive data.

Your responsibilities

You are responsible for the webhook endpoints you configure, the payloads you send, the credentials and custom headers you store, the automations you trigger, and the downstream effects of those automations.

You should keep webhook URLs, bearer tokens, API keys, signing secrets, and similar credentials private. If a credential is exposed, rotate it with the destination provider. Use HTTPS endpoints where possible, and avoid sending sensitive data to systems that are not designed to protect it.

You are also responsible for complying with the terms, policies, rate limits, security requirements, and data-protection rules of any third-party service you connect to ShareToWebhook.

Acceptable use

Do not use ShareToWebhook to send spam, malware, phishing content, abusive content, illegal material, content that infringes someone else's rights, secrets you are not authorised to process, or payloads designed to disrupt, overload, probe, or bypass third-party systems.

Do not use ShareToWebhook to attack endpoints, evade rate limits, scrape systems without permission, exfiltrate data, impersonate someone else, or trigger automations that you know or should know will cause harm.

We may limit, suspend, or terminate access if we believe ShareToWebhook is being misused, if required by law or a platform provider, or if continued access creates risk for the product, users, third parties, or infrastructure.

Third-party services

ShareToWebhook can be used with services such as Zapier, Make, n8n, Slack, Hermes, Cloudflare Workers, custom HTTP endpoints, and other tools that accept webhook requests. Those services are not controlled by ShareToWebhook.

Third-party services may change their APIs, security rules, rate limits, pricing, payload handling, logging, or retention. ShareToWebhook is not responsible for third-party services, their availability, their handling of your data, or the results of workflows they run.

If a third-party service rejects, logs, transforms, stores, deletes, shares, or acts on a payload, that is governed by your relationship with that provider.

Subscriptions, pricing, and app stores

ShareToWebhook may offer free and paid plans. Plan limits, features, and prices may change over time. Paid access covers the features available for the plan and period purchased, not any permanent right to a specific feature, platform, integration, or price.

ShareToWebhook Pro subscriptions and lifetime purchases made in the mobile app are sold through the Apple App Store or Google Play, depending on where you purchased them. Payment is charged by the applicable app-store account at confirmation of purchase. Apple, Google, RevenueCat, and related payment infrastructure may process purchase records, renewal status, tax information, fraud-prevention signals, and subscription events needed to provide paid access.

Auto-renewing subscriptions renew automatically unless cancelled before the end of the current billing period. You can manage or cancel an active subscription through your App Store or Google Play account settings. When available in the app, the Manage subscription option opens the platform-native subscription management screen. You can also use Restore purchases to ask the app store and RevenueCat to refresh your entitlement status.

Refunds and cancellations

Cancellation stops future renewal. Unless required by applicable law or the applicable app-store policy, cancelling a subscription does not refund the current billing period, and Pro access continues until the end of the paid period.

Refund requests for purchases made through the Apple App Store must be submitted to Apple. Refund eligibility is determined by Apple and applicable law.

Refund requests for purchases made through Google Play may be handled by Google Play or, where available, by ShareToWebhook according to Google Play policies and applicable law.

If you believe a purchase did not unlock correctly, contact us at [email protected] or use the contact form. We can help investigate, restore access, or point you to the correct app-store refund process, but we cannot guarantee refunds outside the applicable store process.

Support and feedback

We may provide support by email, contact form, documentation, or other channels. Support availability and response times are not guaranteed, especially during preview and beta periods.

If you send feedback, suggestions, bug reports, feature ideas, payload examples, screenshots, or diagnostic information, you give us permission to use that information to understand, improve, support, and develop ShareToWebhook. Do not send secrets or sensitive data unless it is necessary and you are authorised to share it.

Privacy

The privacy policy explains what ShareToWebhook collects and what it does not collect. In particular, the core direct-send workflow does not send your webhook payloads or endpoint settings through ShareToWebhook servers.

Availability and disclaimers

ShareToWebhook is provided as is and as available. We do not promise uninterrupted access, error-free operation, compatibility with every device or webhook destination, preservation of local configuration, or successful delivery of any webhook request.

To the maximum extent permitted by law, ShareToWebhook disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, and any warranties implied by course of dealing or usage of trade.

Limitation of liability

To the maximum extent permitted by law, ShareToWebhook will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, failed automations, business interruption, downstream actions, or third-party service failures.

Where liability cannot be excluded, it will be limited to the greater of the amount you paid for ShareToWebhook in the 12 months before the claim or GBP 20.

Termination

You can stop using ShareToWebhook at any time. We may suspend or end access to the website, mailing list, preview, beta, app, extension, or paid service if you breach these terms, misuse the product, create risk for others, or if we discontinue the relevant feature or service.

Governing law

These terms are governed by the laws of Scotland, except where local consumer law gives you mandatory rights that cannot be changed by contract.

Changes

We may update these terms as the product, pricing, legal requirements, app platforms, and service model change. If a change materially affects how ShareToWebhook works or what you can expect from it, we will make reasonable efforts to make the updated terms available before or when the change takes effect.

Contact

For questions about these terms, email [email protected] or use the contact form.