Terms of Service

Last updated: 2026-07-13

1. Acceptance of Terms

By accessing and using PayloadRelay, you accept and agree to be bound by the terms and provision of this agreement. If you do not agree to abide by the above, please do not use this service.

2. Service Description

PayloadRelay is a webhook relay service that allows users to receive incoming webhook requests and fan them out to multiple configurable targets, including HTTP webhooks, email, Slack, Discord, Google Sheets, Microsoft Teams, PagerDuty, and Telegram. The service provides tools for endpoint management, payload transformation and filtering, message templates, routing filters, failover delivery, and activity monitoring.

PayloadRelay also supports email ingestion: endpoints can receive inbound email at a dedicated address and convert it into JSON payloads dispatched to your configured outputs. For email delivery targets, customers may choose between platform-managed delivery or bring their own SMTP server (custom SMTP relay).

3. User Accounts

To access certain features of the service, you may be required to register for an account. You can sign up using an email address and password, or via third-party OAuth providers (Google, Microsoft, or Apple). You are responsible for safeguarding your credentials and maintaining the confidentiality of your account.

  • You must provide accurate and complete information when creating an account
  • You are responsible for all activities that occur under your account
  • You must notify us immediately of any unauthorized use of your account

New accounts begin with a 14-day Team trial. No card is required. When the trial ends, the workspace continues on the permanent Sandbox plan unless you subscribe to a paid plan.

4. Paid Subscriptions and Billing

Paid plans are priced and charged in United States dollars (USD). Advertised prices exclude applicable sales tax, VAT, or similar charges. Stripe calculates tax from the billing information you provide.

  • Subscriptions renew automatically for the selected monthly or annual term until canceled.
  • By subscribing, you authorize PayloadRelay and Stripe to charge the selected payment method for recurring fees, applicable taxes, and confirmed prorated upgrades.
  • Higher-tier changes and monthly-to-annual changes take effect after you confirm the displayed proration and Stripe confirms payment.
  • Downgrades and annual-to-monthly changes take effect at the next renewal. Resources above the new plan limits may be deactivated then.
  • Cancellation stops future renewal. Paid features continue through the current term, after which the workspace moves to Sandbox, unless a refund is legally required or separately approved.
  • Fees are non-refundable by default, including unused time in a billing period, except where applicable law requires otherwise or PayloadRelay expressly approves a refund.

If a recurring payment fails, PayloadRelay ordinarily provides a seven-day recovery period. Access may end sooner if Stripe reports the subscription as unpaid or canceled. You can update payment details, view invoices, and cancel through the Stripe billing portal.

This billing section should be reviewed by qualified legal and tax advisers before commercial launch.

5. Acceptable Use

You agree not to use the service for any unlawful purposes or in any way that could damage, disable, overburden, or impair the service.

  • Do not attempt to gain unauthorized access to any part of the service
  • Do not use the service to transmit malicious code or content
  • Do not interfere with or disrupt the service or servers
  • Do not use the service for any illegal activities
6. Data and Privacy

Your privacy is important to us. Please review our Privacy Policy, which also governs your use of the service, to understand our practices.

By using our service, you consent to the collection and use of information as outlined in our Privacy Policy.

Payload bodies are processed in delivery and retry queues as needed to forward accepted events. They are not written to the metadata-only activity trail (endpoint, outcome, originating IP address, error reason, and delivery outcome), which is retained for 30 days and then automatically deleted. Failed queue messages may remain in operational dead-letter queues until they are remediated or purged.

Sensitive configuration data — including webhook secrets, auth forwarding credentials, and SMTP passwords — is encrypted at rest using AES-256 encryption.

7. Service Availability

We strive to maintain high availability of our service, but we cannot guarantee uninterrupted access. The service may be temporarily unavailable due to maintenance, updates, or technical issues.

8. Limitation of Liability

In no event shall PayloadRelay be liable for any indirect, incidental, special, consequential, or punitive damages, including without limitation, loss of profits, data, use, goodwill, or other intangible losses.

9. Termination

We may terminate or suspend your account and bar access to the service, under our sole discretion, for any of the following reasons:

  • Trial completion — accounts receive a 14-day Team trial with a visible countdown and move to Sandbox when it ends
  • Subscription cancellation — paid subscribers retain paid features through the current billing period and then move to Sandbox
  • Payment failure — service ordinarily remains available for a seven-day recovery period unless Stripe reports the subscription as unpaid or canceled sooner
  • Breach of these Terms or engaging in abusive, fraudulent, or illegal activity — may result in immediate termination without prior notice
10. Intellectual Property

You retain all rights to the data you transmit through PayloadRelay. We claim no ownership over your webhook payloads or any content relayed through the service.

The PayloadRelay service, its original content, features, and functionality are and will remain the exclusive property of PayloadRelay and its licensors.

11. Usage Limits

Your use of the service is subject to the usage limits of your subscription plan. Limits vary by tier (Sandbox, Team trial, Solo, Team, Scale, and Unlimited) and may include:

  • Monthly accepted-event quota: a maximum number of accepted webhook or email events per calendar month. One accepted event counts once; destination fan-out and retries do not consume additional accepted-event quota. Enabled non-failover outputs and retry attempts are subject to separate plan limits. Quotas reset on the first day of each month.
  • Active endpoint limit: a maximum number of endpoints that can be enabled at once.
  • Output limit: a maximum number of enabled, non-failover outputs per endpoint. Disabled output configurations and failover destinations do not count.
  • Payload size limit: accepted payloads, including email-derived events, are capped at 256 KB on Sandbox and Solo, 512 KB on the Team trial and Team, and 1 MB on Scale.
  • Retry attempts and policies: attempts are capped per tier. Sandbox and Solo use the standard schedule; Team trial, Team, Scale, and Unlimited can select advanced schedules and custom retry status codes.

Exceeding your monthly accepted-event quota results in new events being rejected until the next monthly reset or until you upgrade. Trial completion and paid cancellation move the workspace to Sandbox. Past-due accounts remain subject to the payment-recovery and read-only rules described above.

12. Organizations and Shared Data

PayloadRelay supports multi-user organizations where members share endpoints, relay targets, activity logs, and subscription quotas within the same workspace.

  • All members of an organization can view endpoints and request logs belonging to the organization, subject to their assigned role (owner, admin, user, or viewer)
  • Organization members are invited via email by the organization owner or admins
  • Usage quotas (requests, endpoints) are shared across all members of the same organization
  • The number of users per organization is subject to your subscription tier limits

By joining an organization, you acknowledge that other members may access endpoint configurations and activity data within that workspace.

13. Indemnification

You agree to defend, indemnify, and hold harmless PayloadRelay and its officers, directors, employees, and agents from and against any claims, liabilities, damages, losses, and expenses arising out of or in connection with your use of the service or violation of these Terms.

14. Governing Law

These Terms shall be governed by and construed in accordance with the laws of Norway, without regard to its conflict of law provisions. Any disputes arising under these Terms shall be subject to the exclusive jurisdiction of the courts of Norway.

15. Changes to Terms

We reserve the right to modify or replace these Terms at any time. If a revision is material, we will provide at least 30 days notice prior to any new terms taking effect.

16. Contact Information

If you have any questions about these Terms of Service, please contact us at:

© 2026 PayloadRelay. All rights reserved.