Security and data handling
Captured request data
New captures preserve raw body bytes with a SHA-256 fingerprint. Pretty views and header masking do not change stored evidence. Bodies are limited to 128 KiB. Captured HTML is displayed as code.
Captured payloads are not encrypted by HookWatcher itself, and the service does not currently promise private encrypted payload storage. Treat webhook URLs and payload links as sensitive: some links work for anyone who has them.
In the app, request data is returned only to signed-in members of the endpoint's workspace, or to the browser session that created an anonymous endpoint. Three things work for anyone who has the link, without signing in or belonging to the workspace: an endpoint an Owner or Admin has made public (Team and Enterprise), a share link (it expires after 1 hour to 30 days, can require a password, can be revoked, and redacts credentials and, by default, personal data), and the link to a request's generated documentation.
Secrets and account security
The inspector masks common credential headers by default and allows temporary reveal. Masking is not storage redaction. Avoid sending production credentials or personal data in test payloads. Accounts support authenticator-app MFA and password reset. Application-level encryption of all stored secrets is not currently implemented. Provider signing secrets for Stripe/GitHub verification are encrypted by HookWatcher before they are stored and are never shown again after saving.
Access keys, workspaces and tunnels
API keys are shown once and can't be displayed again. Each key has scopes, can be limited to specific endpoints, can expire and can be revoked. hwcli sign-ins are separate sessions that expire and can be revoked from the Developer page or with hwcli logout.
Workspace access is checked on every request against the member's role. Endpoints in a workspace you don't belong to answer as not found. Requests to a tunnel are passed to hwcli on your machine; HookWatcher keeps the tunnel's name, connection status and monthly totals, not the requests themselves. Request history for tunnels is stored only on your computer.
Replay and forwarding
Replay requires a signed-in workspace member with the Owner, Admin or Developer role; Viewers can inspect but not send. Replay, edited replay, forwarding, destination tests and retries only reach public HTTP(S) addresses: localhost, private networks and cloud metadata addresses are refused, every delivery is checked again before it is sent, redirects are not followed, and time and response size are limited.
Retention and deletion
Plan limits determine configurable retention. Requests past their retention period are removed by scheduled cleanup. A deleted request disappears at once and is then removed from storage; deleting history also removes associated replay and forwarding attempts. Temporary processing copies and backups follow their own schedules, so immediate erasure from them is not guaranteed.
Review retention limitsTransport and reporting
Connections to HookWatcher use HTTPS. No SOC 2, ISO 27001 or HIPAA certification is claimed here.
Report a suspected vulnerability through the contact information on the About page. Do not include captured secrets in a public report.
Destination checks in practice
These verdicts come from the same validation the forwarding settings use.
https://api.example.com/hooksAllowed. DNS is checked again on every delivery.
http://localhost:3000/webhooksLocalhost and private network destinations cannot be used for webhook forwarding.
http://192.168.1.10/hooksPrivate or local network destinations are not allowed.
http://169.254.169.254/latest/meta-dataPrivate or local network destinations are not allowed.