Privacy Policy
SignalBin collects and stores the data needed to run accounts, workspaces, webhook inspection, billing, email, security, and support. This is product policy draft copy, not legal advice.
Account dataWe collect account details such as email address, password authentication data, email verification state, session data, password reset activity, and workspace membership.
Workspace dataWe store workspace names, slugs, settings, invited teammates, endpoint names, endpoint slugs, endpoint secrets, and configuration needed to route incoming webhooks.
Webhook dataWhen a request reaches a SignalBin endpoint, we may store request metadata, headers, query strings, detected body type, raw body, parsed body previews, files, byte counts, source information, and received timestamps.
Billing dataWe store traffic credit, usage, ledger entries, traffic-pack purchases, checkout references, provider event IDs, payment status, currency, amount, and related billing metadata.
Email and support dataWe may store transactional email activity for account verification, password reset, invites, billing messages, and support or operational communications.
How we use dataWe use this data to authenticate users, route webhook traffic, display request history, enforce limits, process billing, send service emails, troubleshoot issues, and prevent abuse.
SharingWe share data with service providers that help operate SignalBin, such as hosting, email, billing, payment, observability, and support providers, and when required for legal or security reasons.
Retention and deletionWebhook history, files, account records, and billing records are retained while needed to provide the service, meet operational requirements, resolve disputes, comply with law, or prevent abuse.
Your choicesYou can choose what data your systems send to SignalBin endpoints, remove endpoints from use, manage workspace access, and contact support about account or workspace data.