webhooklocal
Effective 6 October 2026

Privacy policy

This page lists what webhooklocal stores, why, for how long, and who else sees it. The service is operated by Anil, an individual developer in India. Questions and requests: [email protected].

1. What is stored

DataWhyKept
Your email address, and your GitHub user ID if you sign in with GitHubTo sign you in and send account noticesUntil you delete your account
Sign-in links: the address they were sent to and a hash of the linkTo complete a sign-inExpire after 15 minutes; removed within a day
Browser sessions: a hashed session ID and the browser's user-agent stringTo keep you signed in30 days, or until you sign out
CLI tokens: a hash of the token, the device name you gave it, when it was created and last usedTo let the wl tool act for your accountUntil you revoke it or delete your account
Webhook requests: method, path, query, headers, body, the sender's IP address, and the time receivedThis is the service: showing you, forwarding, and replaying what a provider sentBy plan: 24 hours and 100 requests on Free, 30 or 90 days on paid plans; or until you delete the request, the endpoint, or your account
Replays: where the request was sent, the result, and the timeTo show the history of a requestSame as the request

Webhook bodies often contain personal data about your customers and secrets from your providers. You decide what is sent to your URL, and you are responsible for having the right to process it. The service stores the full request as received; headers such as Authorization are hidden in the dashboard until you reveal them, but they are stored.

2. What is not stored

  • Visitors' IP addresses are used for rate limiting in memory only. They are not written to disk or to the logs. The exception is the sender's IP on a stored webhook request, listed above, which is part of the request you asked to capture.
  • The web server keeps no access logs. Application logs record errors and the paths that caused them, never email addresses or request bodies.
  • No advertising, tracking pixels, or profiles. The sign-in email contains no tracking links.

3. Cookies and analytics

One cookie, wl_session, is set when you sign in and removed when you sign out. It is not readable by scripts and is only sent to webhooklocal.com. The dashboard stores a few interface preferences (such as which editor view you last used) in your browser's local storage; they never leave your browser.

The public pages (home, pricing, docs, and this page) use Cloudflare Web Analytics to count page views. It sets no cookies and stores nothing in your browser. The dashboard has no analytics script.

The sign-in form includes Cloudflare Turnstile, which decides whether a visitor is a bot. Turnstile is provided by Cloudflare under its privacy policy.

4. Who else processes the data

ProviderWhat it doesWhere
Amazon Web ServicesRuns the server and database, and stores encrypted database backupsFrankfurt, Germany; US company
CloudflareProxies all traffic to the site, serves DNS, runs Turnstile and Web Analytics, and forwards mail sent to webhooklocal.com addressesGlobal network; US company
ResendSends the sign-in emailsEU region (Ireland); US company
PaddleCheckout and subscriptions, only if you upgrade: Paddle collects your card and billing address itself; webhooklocal receives your Paddle customer and subscription ids, the plan, its status and renewal date.UK and US company
GitHubSign in with GitHub, only if you choose it. webhooklocal receives your GitHub user ID and the primary email on your GitHub account.US company

Because Cloudflare sits in front of the site, every request to a webhook URL passes through it. Cloudflare's own handling of that traffic is covered by its policy, linked above. No other third party receives your data, and nothing is sold or shared for advertising.

5. Backups and location

The database lives in Germany. A verified backup is taken every night and kept for up to 35 days, so data you delete disappears from backups within that time. Backups are protected the same way as the live database.

6. Your rights and controls

  • See your data. Your requests, replays, and CLI tokens are visible in the dashboard. Browser sessions are not listed there; signing out ends the one in that browser. For a copy of everything stored for you, including sessions, in machine-readable form, email [email protected].
  • Delete. Delete a single request, all requests of an endpoint, an endpoint, or your whole account from the dashboard. Deletion is immediate; backups age out as above.
  • Correct. Your email address can be changed by emailing the address above from the current one.

If you are in the European Union, the United Kingdom, or India, the GDPR, the UK GDPR, or the Digital Personal Data Protection Act give you these rights by law, including the right to complain to your data protection authority. For the content of webhook requests, you are the controller and webhooklocal is your processor: the data is stored and forwarded on your instructions and used for nothing else.

7. Security

Traffic is encrypted in transit. Session IDs and tokens are stored as hashes. The server accepts connections only through Cloudflare. How to report a vulnerability is on the docs security section; the address is [email protected]. If a breach affects your data you will be told by email without undue delay.

8. Changes

Changes are posted here with a new effective date. If a change affects what is collected or who processes it, you will be told by email first.

See also the terms of service.