This policy explains what data SignalHub receives when users access the website and service, why the data is processed, when it may be shared, and how users can contact us about privacy requests.
If a user submits recipient or employee data, the user is responsible for having a lawful basis to do so.
1. General
SignalHub processes data needed for registration, authentication, event delivery, billing, support, security, and service reliability. This policy applies to the website, account area, API, webhooks, integrations, and support requests.
2. Data we may process
- account data such as name, email, billing country, and interface language;
- access data such as password hashes, sessions, tokens, and email verification status;
- service settings such as sources, channels, recipients, integrations, API keys, and webhook settings;
- event data such as payloads, levels, priorities, subjects, message text, delivery metadata, and errors;
- billing data such as selected plan, currency, payment status, and technical payment identifiers;
- technical data such as IP address, user agent, request time, error logs, and security events.
3. Purposes
Data is used to provide the service, route and deliver notifications, display message history, calculate limits and billing, prevent abuse, diagnose errors, respond to support requests, and meet legal obligations.
4. Cookies, logs, and analytics
The website and account area may use required cookies for authentication, form protection, sessions, locale selection, and interface operation. Technical logs are used for security, diagnostics, delivery troubleshooting, and abuse prevention.
5. Sharing data
SignalHub may share necessary data with infrastructure, email, communication, payment, monitoring, and support providers that help operate the platform. Data may also be disclosed when required by law or needed to protect rights and security.
6. Retention
Data is stored for as long as needed for the account, delivery history, billing, security, accounting, and dispute resolution. Some records may be retained longer when required by law or operational security.
7. User rights
Users may contact support to request access, correction, export, restriction, or deletion of personal data. SignalHub may request identity confirmation and may limit requests where security, accounting, fraud prevention, contractual, or legal obligations apply.
8. Security
SignalHub uses technical and organizational safeguards such as access controls, password hashing, session controls, security logs, and operational monitoring. Users should also protect passwords, API keys, webhook URLs, and integration tokens.
9. Contact
Privacy requests can be sent through account support or to support@signalhub.pro.