Privacy policy
Last updated
This policy covers the hosted Webhook Trap service at app.webhooktrap.dev. If you run Webhook Trap on your own server, your data stays with you and this policy does not apply: the operator of that instance is responsible for it.
1. Who runs Webhook Trap
Webhook Trap is an open-source project (AGPL-3.0) run by Jiordi Kengne, who is the data controller for the hosted service.
Questions, requests about your data and complaints: privacy@webhooktrap.dev.
2. What we collect
Account data
- Your email address and, if you give one, a display name.
- Your password, if you set one, stored only as an argon2id hash.
- If you sign in with GitHub or Google: the account id the provider gives us, whether it says your email is verified, and your provider login or email to show you which account is linked. We ask only for your email address and basic profile. We get no access to your repositories, contacts or files, and we do not store your avatar.
Passkeys and two-step sign-in
- Passkeys and security keys: the public key, the credential id, the name you give it and when it was last used. The private key never leaves your device.
- Authenticator apps: the shared secret, stored encrypted.
- Recovery codes, stored only as hashes.
Captured webhook requests
When a provider (or anyone) sends a request to one of your capture URLs, we store it so you can inspect and replay it: method, path and query, headers, the body (up to 5 MiB; above that, only its size and hash), and the source IP address. The values of Authorization, Proxy-Authorization and Cookie headers are replaced by a placeholder before storage. What the body contains depends on what your provider sends; it may include personal data about your own customers. You decide what you point at a capture URL.
Run results
When you prove a handler against provider scenarios, we store the run plan, the deliveries, the outcomes and the findings. Your provider signing secrets and raw probe values stay on the machine running the agent; the server stores only display forms of results.
Guest sessions
You can try Webhook Trap without an account. A guest session is a random token in a cookie, stored only as a hash, with the captures and runs made in it. It lasts 24 hours.
Security log
We record security events on your account, such as sign-ins, failed attempts, password changes and added or removed keys, with the time, a short browser label (for example "Firefox on Linux") and a shortened network address (IPv4 /24 or IPv6 /48; the full address is not kept). You can see this log in your account settings.
3. How we use it
- To sign you in and keep your account secure.
- To store, show and replay the webhooks you capture, and to run the scenarios you start.
- To send you account emails: confirming your address, resetting a password, security alerts, and confirming an account deletion.
- To enforce rate limits and quotas and stop abuse.
The legal bases are the contract with you (providing the service you signed up for) and our legitimate interest in keeping it secure.
We do not sell your data, show ads, or use third-party analytics or trackers. The app loads no analytics scripts.
4. How long we keep it
- Captures: per project, you choose 1, 7, 14 or 30 days (30 by default). Older captures are deleted daily.
- Runs: per project, you choose 7, 30 or 90 days (90 by default).
- Deleted projects: erased for good 24 hours after you delete them.
- Guest sessions: 24 hours from creation, then deleted with everything in them, unless you move them into an account when you sign up.
- Security log: 1 year.
- Your account: until you delete it.
Deleting your account
You can delete your account in your settings. We ask you to confirm it: with a second factor if you use one, otherwise through a link sent to your email address. The account is closed at once and erased from the live database within 1 hour: projects, captures, runs, keys, sessions and linked sign-in methods. Security log entries about the account are kept for the rest of their year with the email address masked.
We keep a short deletion record (an internal account id and the time of deletion, never your email address) so a restore from backup can never bring a deleted account back.
Backups
Backups are encrypted and kept for 14 days (point-in-time recovery covers the last 7). Deleted data leaves the backups within 14 days.
5. Where it is stored and who processes it
- Contabo: the server running the app and database, in the EU (Germany).
- Cloudflare: DNS for webhooktrap.dev, and R2 storage for encrypted backups.
- PulseSend (delivering through Amazon SES): sends account emails. It receives your email address and the message.
- GitHub and Google: only if you choose to sign in with them. Their own privacy policies apply to what you share with them.
We share data with no one else, except when the law requires it.
6. Cookies
We use only cookies the service needs. No tracking cookies.
__Host-wt_session: your signed-in session (encrypted).__Host-XSRF-TOKEN: protects forms against cross-site request forgery.__Host-wt_guest: set only when you start a guest session.appearance,layout,layout_sidebar,sidebar_state: set only when you change the theme or layout, to remember your choice on this device.
7. Your rights
Under the GDPR and similar laws you can ask to access, correct, export or delete your data, object to or restrict its use, and complain to your data protection authority.
- Access and correction: your account settings show your email, sign-in methods, keys, sessions and security log, and let you change them.
- Deletion: delete captures, projects or your whole account yourself at any time.
- Export and anything else: write to privacy@webhooktrap.dev. We answer within 30 days.
8. Children
Webhook Trap is a developer tool and is not meant for anyone under 16. We do not knowingly collect data from children. If you think a child has an account, write to us and we will delete it.
9. Security
All traffic uses HTTPS. Passwords and recovery codes are hashed, authenticator secrets are encrypted, and backups are encrypted. No system is perfectly secure; if we learn of a breach that affects your data, we will tell you without undue delay.
10. Changes to this policy
We will update the date above when this policy changes. For significant changes we will tell account holders by email before they take effect. See also the Terms of service.