webhookhub

Document version : 2026-11-20

Privacy and personal data

This policy describes how account data and webhook data are processed. The controller for account data is the publisher identified in the legal notice.

Data and purposes

Your name, email, the acceptance date and version of the terms, authentication information, sessions and desktop installation metadata are used to provide and secure access. A name, email and authentication method are needed to create an account. You can sign in with your email and password or a single-use magic link. Two-factor authentication is optional. Passwords and access tokens are hashed; two-factor secrets are protected by application encryption.

Incoming requests

Request URLs, parameters, headers, IP addresses and bodies are recorded. Uploaded file contents are not stored separately, only their metadata; however, the raw HTTP body can contain multipart data sent by the caller. Content is available to the webhook owner and desktop apps they authorize. It may include third-party data or secrets: prefer test data and remove unnecessary information before sending. Anyone who knows a webhook URL can send requests to it.

Roles and legal bases

Account management and delivery of the requested service rely on performance of that service. Security and abuse prevention rely on the legitimate interest in protecting the service and its users. For third-party personal data in webhooks, users determine purposes and must establish an appropriate legal basis; the publisher acts on their instructions. The data processing agreement must be completed and agreed before such use.

Retention

Account data remains until account deletion. Configured retention is 30 days for incoming requests, 1 day(s) for expired desktop authorizations, and 30 days for revoked or expired access records. Sessions expire after 120 minutes of inactivity. Daily cleanup must be active to enforce these periods, with a technical delay until the next run. Production application logs rotate over 14 daily files; failed broadcasts are pruned after 7 days. Backup and hosting log policies are detailed below.

Recipients and transfers

The publisher and technical providers access data as necessary for hosting, email delivery and security. Providers and countries are listed below. Any transfers outside the European Economic Area and their safeguards must be specified before launch. The service does not use data for targeted advertising.

Your rights

You can request access, correction, erasure and restriction, and, where applicable, portability or objection. Your profile lets you update information, export data and delete your account. Send other requests to the privacy contact. Proportionate identity checks may be needed; do not send identity documents unless requested. Replies are normally provided within one month, with a reasoned extension in the circumstances permitted by the GDPR. You can complain to the French supervisory authority, CNIL.

Traffic statistics

The publisher uses a self-hosted Umami instance at umami.alexandre.re to understand traffic and improve the service, without tracking cookies or targeted advertising. Pages are grouped without their identifiers and sensitive links are filtered before submission. Statistics retention is managed in the Umami instance, separately from webhook retention periods. Technical logs on the analytics server also depend on its hosting configuration. For questions or requests about these statistics, use the contact listed in the legal notice.

Automated decisions

The service does not perform automated decisions with legal effects or advertising profiling. Rate limits and security checks protect access to the service.