Terms of Use

Using Hooksbase

These Terms govern access to Hooksbase, including the marketing website, dashboard, API, SDK, CLI, public ingest endpoints, email and form ingest, scheduled webhooks, Automations, event drains, and related services. By creating an account, using an API key, sending events to Hooksbase, or using the dashboard, you agree to these Terms.

Hooksbase is event infrastructure for teams that need to ingest, route, transform, replay, observe, and deliver events to HTTP endpoints and supported cloud destinations. You are responsible for deciding whether Hooksbase is appropriate for your workload and for configuring your projects, webhooks, destinations, credentials, transforms, Automations, and retention settings.

Accounts and organizations

You must provide accurate account information and keep your login credentials secure. Hooksbase supports email and password login, optional Google or GitHub login when enabled, organization membership, and project-scoped access. Actions taken through your account, organization, browser session, or project API keys are your responsibility.

If you invite other users to an organization or project, you are responsible for managing their access. Service-admin access is reserved for Hooksbase operational staff and is not a customer entitlement.

API keys and secrets

Project API keys, webhook ingest secrets, signing secrets, destination credentials, custom headers, Automation egress credentials, and similar secrets must be protected. Hooksbase returns some secrets only when they are created or rotated. You are responsible for storing them securely, rotating them when needed, and revoking access that should no longer be active.

Do not share API keys or secrets in public repositories, client-side code, logs, tickets, or other places where they can be exposed. If you believe a secret has been compromised, rotate or revoke it promptly and contact us if you need operational assistance.

Customer content

Customer content includes event payloads, headers, files, email and form submissions, provider metadata, destination configuration, Automation code, logs, run results, drain configuration, credentials you submit, and related project data. You retain ownership of your customer content.

You grant Hooksbase the rights needed to operate the service for you, including receiving inbound events, validating and storing payloads, applying routing and transforms, running Automations, dispatching events to configured destinations, retrying delivery, supporting replay and DLQ recovery, producing usage and operational telemetry, and providing support.

You are responsible for the legality, accuracy, security, and permissions for customer content you send to Hooksbase. Do not send regulated, highly sensitive, or prohibited data unless your agreement with Hooksbase and your own compliance review allow that use.

Delivery behavior

Hooksbase is designed to make event delivery observable and recoverable, but no event platform can guarantee that every destination will accept every request or that every downstream system will behave correctly. Destination outages, network errors, quota limits, invalid credentials, rejected payloads, timeout settings, entitlement limits, and customer configuration can all affect delivery.

Routing uses the source request and configured rules. Transforms and Automations run before the dispatch snapshot is saved. Retries, replays, DLQ re-drives, and bulk replay use persisted delivery snapshots where available, rather than whatever the webhook configuration happens to be later. You remain responsible for idempotency and safe side effects in your receiving systems.

Acceptable use

• Do not use Hooksbase to send spam, phishing, malware, abusive traffic, credential stuffing, vulnerability exploitation, denial-of-service traffic, or unlawful content.
• Do not attempt to bypass authentication, quotas, rate limits, billing controls, destination validation, egress restrictions, or security controls.
• Do not probe, scan, disrupt, reverse engineer, or overload Hooksbase or its infrastructure except as authorized in writing.
• Do not use Hooksbase to process data you do not have the right to collect, transmit, store, transform, or deliver.
• Do not configure destinations, event drains, or Automation egress to target systems you are not authorized to use.

Plans, quotas, and retention

Plans include limits for delivery volume, ingest rate, stored payload bytes, file storage, backlog depth, replay volume, history retention, payload retention, Automations, event drains, and other capabilities. Some features are gated by plan or by enterprise configuration.

Payload, file, delivery-history, audit-log, summary, replay, DLQ, and related retention windows depend on plan, settings, operational safeguards, and enterprise overrides. Retention is a maximum service behavior, not a backup commitment. Data may be unavailable after retention expires, after deletion, after project or webhook destruction, or when required for security or operational reasons.

Premium configuration may remain visible after a downgrade, but runtime use can be blocked until the configuration is cleared or the project is upgraded. Hooksbase may enforce quotas, reject traffic, pause or block features, or fail closed when needed to protect the service.

Billing and overages

Paid self-serve plans are billed through the checkout or billing provider presented in the product, currently Stripe or Polar depending on the deployed environment. You are responsible for subscription charges, applicable taxes, and any metered overage charges you enable or incur under your plan.

Cancelling a subscription stops future renewals according to the billing flow, but it does not automatically refund charges already incurred. Refunds are provided only when required by law or agreed in writing by Hooksbase.

If billing fails, a subscription changes, or a project is downgraded, paid features can be blocked, skipped, paused, or limited. Provider failures for usage-event reporting do not expand your included quota or remove your responsibility for valid usage charges.

Availability and changes

Hooksbase may change, add, suspend, or discontinue features, limits, vendors, APIs, SDKs, CLI behavior, or documentation. We may perform maintenance, respond to incidents, or take action to protect customers, infrastructure, and the service.

We try to keep customer-facing behavior clear in the dashboard, API, documentation, and product pages, but documentation and examples may not cover every configuration or edge case.

Termination

You may stop using Hooksbase at any time. Hooksbase may suspend or terminate access if you violate these Terms, create security or operational risk, fail to pay amounts due, or use the service unlawfully.

After suspension, termination, deletion, or retention expiry, customer content may no longer be available. You are responsible for exporting or draining data you need to keep before it expires or before you stop using the service.

Disclaimers and liability

Hooksbase is provided on an "as is" and "as available" basis, except where a separate written agreement says otherwise. We disclaim warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, and error-free operation to the maximum extent permitted by law.

To the maximum extent permitted by law, Hooksbase will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, lost goodwill, or business interruption. Any aggregate liability is limited to the amounts you paid to Hooksbase for the service during the three months before the claim, unless a separate written agreement states otherwise.

Contact

For questions about these Terms, account access, billing, or service use, contact hello@hooksbase.com.