Terms of Service

These Terms of Service (“Terms”) are an agreement between you and the operator of DeadHook. They govern your access to and use of the DeadHook website, dashboard, APIs, webhook ingestion service, delivery service, documentation, and related features (together, the “Service”).

By creating an account, accessing the Service, or using a paid plan, you agree to these Terms. If you use the Service for an organization, you represent that you have authority to bind that organization. If you do not agree, do not use the Service.

1. Who we are #

DeadHook is an independent software service operated by Jois Andresky, an individual sole proprietor based in Indonesia. DeadHook is not a company, and no company registration number is claimed.

The operator is responsible for the Service. Paddle is the merchant of record for paid transactions and is not the provider of the DeadHook service. Paddle's role is described further in section 10.

2. The DeadHook service #

DeadHook is a webhook reliability service. It receives authenticated webhook requests at customer-configured Source endpoints, records accepted Events, attempts delivery to customer-configured Destinations, exposes delivery attempts, retries eligible failures, and provides dead-letter, replay, archive, and response-inspection workflows.

The Service is intended for developers and organizations that operate their own systems. You are responsible for the integrations, receivers, credentials, and business logic on your side of the connection.

3. Accounts and security #

• You must provide accurate account information and keep it current.
• You are responsible for protecting your password, session, API credentials, Source secrets, Destination signing secrets, and any device used to access the Service.
• You must notify us promptly if you believe your account or credentials have been compromised.
• You must not share an account in a way that defeats organization roles, authentication, or usage limits.
• We may require email verification before certain actions, including accepting invitations.

We may suspend or restrict access where reasonably necessary to protect the Service, other customers, or the public, or where we reasonably believe these Terms have been violated.

4. Organizations and members #

The Service supports Organizations, Projects, and member roles. Organization owners and authorized administrators control membership, projects, Sources, Destinations, billing, and other organization settings. You are responsible for the actions of members you invite and for removing access that is no longer appropriate.

Roles and permissions are enforced by the Service, but no access-control system is infallible. You must configure roles conservatively and review membership regularly.

5. Your webhook data #

You retain ownership of the webhook payloads, Event data, Source and Destination configurations, support messages, and other content you submit (“Customer Data”). You grant DeadHook a limited license to host, process, transmit, inspect, and retain Customer Data as necessary to provide, secure, and support the Service, comply with law, and enforce these Terms.

You are responsible for:

• having a lawful basis and all necessary permissions to send Customer Data to DeadHook and to forward it to your Destinations;
• ensuring your Destinations are authorized to receive the data, and that endpoint permissions and credentials are correct and securely managed;
• minimizing sensitive data and avoiding payloads you are not authorized to process;
• complying with privacy, consumer, financial, health, export, and other laws that apply to your data and your use of the Service; and
• providing any notices and obtaining any consents required for your own end users.

Webhook payloads are supplied by you or your providers. DeadHook does not determine their accuracy, legality, or fitness for your purpose. You should not send government identity documents, full payment-card data, health records, or other highly sensitive information unless you have a lawful basis and appropriate safeguards.

6. Acceptable use #

You must not use the Service to:

• violate any law, regulation, contractual obligation, or third-party right;
• transmit malware, phishing content, spam, fraudulent messages, or content designed to deceive;
• interfere with, probe, scan, overload, or attempt to gain unauthorized access to the Service, other tenants, or third-party systems;
• intercept, alter, or forward data without authorization;
• evade usage limits, authentication, rate limits, billing, or security controls;
• reverse engineer, resell, sublicense, or provide the Service to third parties except as expressly permitted; or
• use the Service for high-risk activities where a failure could reasonably lead to death, personal injury, or severe environmental or financial harm.

We may investigate suspected abuse and may remove content, suspend delivery, or restrict access where reasonably necessary. We may report suspected unlawful activity where required.

7. Delivery semantics #

DeadHook provides at-least-once delivery, not exactly-once delivery. A single accepted Event may produce more than one delivery to a Destination, including when a response is lost, a timeout occurs, a worker is interrupted, or a delivery is retried. Your receiving system must be idempotent and must tolerate duplicate deliveries.

We do not guarantee that every delivery will succeed, that a Destination will process a payload successfully, or that a downstream system will commit its own changes. A successful HTTP response from your Destination is not a guarantee that your application completed its work. You are responsible for monitoring your receivers and for reconciling your own state.

Retries are bounded by the Service's configured policies. Once a Delivery reaches a terminal state, automatic retries stop. Replay is an explicit, audited operation and may be unavailable after payload retention expires or where a Destination is archived or otherwise ineligible.

8. Availability and limitations #

We aim to operate the Service reliably, but we do not promise 100% uptime, uninterrupted access, zero data loss, or recovery of every Event. The Service depends on internet connectivity, cloud infrastructure, database systems, email delivery, Paddle, and your own systems, each of which can fail.

We may perform maintenance, change features, impose reasonable safeguards, or suspend the Service to address security, legal, or operational issues. Where practical, we will provide notice of material planned disruptions. No service-level credit, uptime guarantee, or disaster-recovery objective is offered unless a separate written agreement says so.

9. Free and Pro plans #

The current plans are:

• Free — available now, $0/month: up to 10,000 accepted Events per month, shared across all Free Organizations owned by the same verified user; 3 Sources, 5 active Destinations, and 2 Organization members.
• Pro — planned, $39/month excluding applicable taxes: up to 100,000 accepted Events per month, 20 Sources, 50 active Destinations, and 10 Organization members per Organization. Pro is not yet available for purchase, and no Paddle checkout is enabled.

Limits apply to the Organization as described in the product. An accepted Event is counted once even if a retry or duplicate upstream delivery occurs. Duplicate upstream delivery does not create a second Event or consume quota again. The monthly accepted-Event counter resets at the start of the next calendar month in the Service's configured time basis. Plans, limits, and prices may change prospectively with notice.

If an Organization exceeds a limit, existing accepted work and existing resources are not retroactively deleted by a limit change. New operations that would exceed the applicable limit may be rejected with an error, including HTTP 409. Ingestion may be rejected once a monthly accepted-Event quota is exhausted. Retries and delivery work already accepted continue under the Service's delivery policies.

Destinations that are archived do not count as active Destinations, but existing accepted delivery work is not retroactively canceled merely because a Destination is archived.

10. Paid subscriptions and Paddle #

Pro is planned but not yet available for purchase. No paid subscription can be bought today, no Paddle checkout is enabled, and DeadHook does not currently collect recurring charges.

When Pro launches, Paddle will be the merchant of record for paid DeadHook subscriptions. Paddle will process payments, calculate and remit applicable taxes, handle payment methods, and provide buyer support for payment transactions. DeadHook will provide the software service; it will not be the payment processor or merchant of record for Pro transactions.

The planned Pro price is $39 per month in US dollars, excluding applicable taxes. The amount shown at a future Paddle Checkout, including tax and any localized presentation, will be the amount Paddle presents for the transaction.

Your payment is also subject to Paddle's Buyer Terms (opens Paddle’s website). If these Terms conflict with Paddle's Buyer Terms about a payment transaction, Paddle's Buyer Terms govern that transaction to the extent of the conflict. These Terms govern the DeadHook service itself.

11. Renewal and cancellation #

When Pro launches, subscriptions will renew automatically each month unless canceled before renewal through the Paddle customer portal or another cancellation method Paddle makes available. Cancellation will ordinarily take effect at the end of the current paid billing period. Where a Paddle subscription remains active until that date, paid access continues until the effective cancellation date.

Cancellation will stop future renewal charges. It does not automatically create a prorated refund for time already paid, and it does not retroactively cancel Events or Delivery work already accepted. After the effective cancellation date, the Organization may be moved to the Free plan, subject to the Free limits.

12. Refunds #

No paid transactions are currently available. When Pro launches, Paddle will handle refund requests for Paddle transactions under its Refund Policy (opens Paddle’s website). Refund eligibility will depend on Paddle's policy and any mandatory rights available to you under applicable consumer law. DeadHook will not independently approve or issue refunds for Paddle transactions and does not promise that every request will be approved.

Our Refund Policy explains the customer process, including how to contact Paddle and how to reach DeadHook for product support. Nothing in these Terms or that policy removes a mandatory statutory right that cannot lawfully be excluded.

13. Retention and termination #

Retention periods are described in the Privacy Policy. Raw Event payloads are purged after the configured retention period; Event and Delivery metadata, attempt history, audit records, and support records may remain for operational, security, and legal purposes. Optional response snippets are retained for seven days. Backups may persist for an additional period under the operator's disaster-recovery process.

You may stop using the Service at any time. You may request account or Organization deletion through the contact method in section 18. We may suspend or terminate access for material breach, non-payment, unlawful use, security risk, or where required by law. On termination, access to the Service ends, but provisions that by their nature should survive—including payment obligations, disclaimers, liability limits, and governing law—survive.

14. Intellectual property #

DeadHook, its software, branding, documentation, interface, and service design are owned by the operator or its licensors and are protected by applicable intellectual-property laws. We grant you a limited, non-exclusive, non-transferable right to use the Service during your subscription or permitted free use, subject to these Terms. No ownership rights are transferred.

Customer Data remains yours. You grant the limited processing rights described in section 5. If you provide feedback, we may use it without restriction or obligation, provided we do not disclose your confidential information.

15. Disclaimers and warranties #

To the maximum extent permitted by applicable law, the Service is provided on an “as available” basis. We disclaim implied warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation. We do not warrant that any particular webhook will be delivered, that a Destination will process it, or that data will never be lost or duplicated.

Nothing in these Terms excludes or limits any warranty, guarantee, remedy, or consumer right that cannot lawfully be excluded or limited under applicable law, including mandatory consumer-protection rules.

16. Liability #

This section allocates risk between you and DeadHook. It applies only to the extent permitted by applicable law and is subject to the mandatory exceptions in section 16.5.

16.1 Exclusion of certain damages

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of profits, revenue, business opportunity, or goodwill, arising out of or relating to the Service, even if the party was advised of the possibility.

Loss or corruption of data may be direct or indirect. We do not exclude direct loss of Customer Data caused by our breach of these Terms or our failure to exercise reasonable care. Any such liability remains subject to the cap in section 16.2 and applicable law. To the maximum extent permitted by law, we are not liable for data loss that is indirect or consequential, or that results from your failure to maintain backups, idempotency, reconciliation, or a functioning Destination. Section 15 explains that we do not guarantee zero data loss.

A claim for data loss or other damages requires an applicable legal basis and appropriate evidence of the loss and causation, subject to applicable evidentiary rules. Nothing in this section shifts a burden of proof that applicable law assigns.

16.2 Aggregate liability cap

For this section:

• “Contracting Customer” means the legal person or entity that accepted these Terms and is responsible for the Organization or Organizations giving rise to the Covered Claims. An Organization is an application resource within DeadHook and is not itself a Contracting Customer. A separate legal entity that contracts for its own Organization is a separate Contracting Customer.
• “Claim Group” means all claims by the same Contracting Customer arising from the same underlying event, continuing failure, or series of causally related events, regardless of legal theory, Organization, Event, Delivery, time of assertion, amendment, or reopening. Events are causally related if they share a common root cause, trigger, failed component, configuration, deployment, or form part of one continuous failure. They are not in the same Claim Group merely because they involve the same general product feature, Contracting Customer, or Organization.
• “Earliest Event” means the date of the first underlying event or failure in a Claim Group.
• “Cap Period” means each 12-month period beginning on January 1 and ending on December 31. A Claim Group is assigned to the Cap Period in which its Earliest Event occurred. A later assertion, discovery, amendment, reopening, change in legal theory, additional Event or Delivery, or move between Organizations does not reassign a Claim Group or create a new cap.
• “Measurement Period” means the 12-month period immediately preceding the first day of the Cap Period (the preceding calendar year).
• “Covered Claims” means all claims by the same Contracting Customer in any Claim Group assigned to a Cap Period, regardless of when asserted, the number of incidents, Events, Deliveries, Organizations, or legal theories. Claims by legally distinct Contracting Customers are not aggregated merely because they share an account administrator, billing contact, or technical relationship.

For each Cap Period, DeadHook's aggregate liability to the Contracting Customer for all Covered Claims—whether in contract, tort (including negligence), statute, or otherwise—will not exceed the greater of:

• (a) USD 100; and
• (b) the total applicable Pro subscription fees actually paid by or for that Contracting Customer during the Measurement Period for Pro subscriptions for Organizations controlled by that Contracting Customer.

This is an annual aggregate cap, not a lifetime cap. A genuinely independent incident whose Earliest Event occurs in a later Cap Period is assigned to that later Cap Period and may be subject to that period's cap. The USD 100 amount is not multiplied by the number of Organizations controlled by the Contracting Customer. The cap does not create or guarantee a right to receive USD 100 or any other amount. A Contracting Customer must have a valid legal basis for a claim and must support the claim with evidence of loss and causation, subject to applicable evidentiary rules. The cap limits rather than creates recovery and is subject to section 16.5.

16.3 Customer responsibilities and external dependencies

DeadHook provides at-least-once delivery, not exactly-once delivery. Duplicate deliveries can occur. You are responsible for:

• maintaining functioning webhook Destinations and valid endpoint credentials;
• implementing appropriate idempotency and duplicate-handling in your receiving systems;
• monitoring your receivers, delivery outcomes, and operational alerts;
• performing reconciliation of your own state where appropriate; and
• maintaining business-continuity and backup arrangements for your systems and data.

To the extent a failure or loss is caused by (a) your configuration, code, Destination, network, or failure to monitor, idempotently process, reconcile, or maintain continuity; or (b) third-party infrastructure or services outside our reasonable control, DeadHook is not liable for that failure or loss. These responsibilities affect causation and mitigation; they do not automatically excuse DeadHook's own negligence, breach, or willful misconduct. This allocation does not relieve DeadHook of responsibility for its own acts or omissions, breach, negligence, or willful misconduct, and does not apply to the extent DeadHook caused or contributed to the failure.

16.4 Incident reporting and claims

If you believe a Service failure has caused loss, contact support@deadhook.app promptly after discovery. Include, to the extent reasonably available, the affected Organization, Event or Delivery identifiers, timestamps, affected Destination, a description of the problem, and the impact. Do not send secrets, credentials, or full webhook payloads unless we request them and you are authorized to share them.

We may investigate using available operational records and may ask for reasonable cooperation. A support ticket, failed delivery, downtime, or investigation is not an admission of liability and does not automatically establish a right to compensation. Our investigation is not the final or exclusive determination of legal liability. Failure to report promptly may affect our ability to investigate or mitigate, but does not extinguish rights that cannot lawfully be waived.

16.5 Mandatory exceptions

Nothing in these Terms excludes or limits:

• (a) liability for fraud or fraudulent misrepresentation;
• (b) liability for willful misconduct;
• (c) death or personal injury caused by negligence;
• (d) gross negligence to the extent it cannot lawfully be limited;
• (e) any liability that cannot be excluded or limited by applicable law;
• (f) mandatory consumer-protection rights;
• (g) statutory data-protection remedies.

If a limitation is found unenforceable, it will apply to the maximum extent permitted and the remaining provisions will continue. Nothing in this section prevents you from contacting a regulator, exercising a non-waivable privacy right, or bringing a claim that applicable law permits.

17. Changes to these Terms #

We may update these Terms to reflect changes in the Service, law, security practices, or business model. The revised version will be posted on this page with a new last-updated date and, where required, a new effective date. Material changes will be communicated through the Service or by email where appropriate. Continued use after the effective date means you accept the revised Terms, to the extent permitted by law. If you do not agree, stop using the Service and cancel any paid subscription.

18. Governing law and contact #

These Terms are governed by the laws of Indonesia, without regard to conflict-of-law rules, except where mandatory consumer law in your place of residence gives you a more favorable right. Subject to those mandatory rights, disputes may be brought before the competent courts of Indonesia. Before starting a formal dispute, please contact us so we can try to resolve the issue.

DeadHook is operated by Jois Andresky, based in Indonesia. Public contact: support@deadhook.app. Existing customers can also use Support.

For privacy requests, please use the contact process in the Privacy Policy. For payment transactions, Paddle's buyer support is the appropriate first contact.