Terms of use

1. Registration and access

To use SignalHub, the user creates an account, confirms an email address, and provides information required for service operation and billing. A user acting for an organization confirms authority to use the service for that organization.

1.1. Account data

The user must provide accurate data, must not impersonate another person, and must not create accounts to evade limits or restrictions.

1.2. Access security

The user is responsible for passwords, API keys, webhook URLs, bot tokens, and other secrets. Compromised keys should be revoked or replaced in the interface.

2. Using the service

SignalHub lets users create delivery channels, connect sources, add recipients, and review message statuses. The user configures routing, priority, recipient lists, and delivery rules.

• A source sends an event to SignalHub through a supported connection method.
• A channel determines where and how the notification is delivered.
• Message history helps diagnose statuses, errors, retries, and delivery behavior.

3. Acceptable use

The service is intended for legitimate operational notifications, infrastructure monitoring, product events, customer support, billing, and similar workflows.

SignalHub must not be used for spam, fraud, malicious content, unlawful advertising, scraping, infrastructure attacks, or violation of third-party platform rules.

4. Content and recipient data

The user is responsible for event payloads, templates, subjects, recipient addresses, and other data submitted to SignalHub. If the user adds third-party data, the user must have a lawful basis for doing so.

5. API and integrations

APIs and integrations must be used within published limits, plan limits, and technical documentation. Attempts to bypass limits, overload the platform, use another user's tokens, or access another user's data are prohibited.

6. Support, availability, and liability

SignalHub aims to maintain stable operation, but it does not guarantee uninterrupted availability of every channel or external integration. Planned maintenance, provider outages, network failures, and user configuration can affect delivery.

The service must not be used as the only channel for emergency, medical, rescue, or legally mandated notifications that require guaranteed delivery.

7. Changes and termination

The user may stop using the service by removing integrations and contacting support about account questions. SignalHub may restrict access for violations, security risks, unpaid use, or abuse. Updated terms are published on this page.

8. Contact