What Security Means to Us
What security means at HookDeploy: break-glass access, weekly-rotating encryption keys, fail-closed architecture, and hardware-key-only staff access.
Every webhook that passes through HookDeploy could be a Stripe payment event, a patient record update, a user’s password reset token, or a signed contract notification. We see the raw payloads of the systems our customers run their businesses on. That’s not a footnote in our architecture. It’s the starting point for every decision we make.
Here’s what that actually looks like in practice, not as marketing copy, but as engineering constraints we hold ourselves to.
We don’t want your data
The simplest security principle is the one most companies ignore: if we don’t need to have your data, we don’t want it. Every payload we touch is a liability we’re choosing to hold on your behalf, not an asset we get to keep. That shapes retention windows, it shapes what we log, and it shapes what we build features around. Data minimization isn’t a compliance checkbox for us. It’s the actual goal.
Break-glass access, from day one
Support staff don’t get standing access to customer data. Access to any specific account’s detailed configuration requires an explicit, time-boxed break-glass grant, logged and auditable. This wasn’t bolted on after a scare or added ahead of a compliance audit. It was part of the admin architecture from the first line of code, because “we’ll fix access control later” is how breaches happen.
Encryption that actually protects you
All data at rest is encrypted with AES-256-GCM, using org-scoped keys that rotate weekly. Scoping keys per organization means a key compromise doesn’t cascade across every customer we have. Weekly rotation means a stolen key has a short shelf life. And we’re building toward BYOK (bring your own key) support, so customers with their own key management requirements can hold the keys themselves, not just trust that we’re holding them well.
Fail closed, not fail open
This is the principle we care most about, because it’s the one that’s easy to get wrong under pressure. If encryption fails for any reason, the webhook still gets forwarded to its destination. Availability for your integrations doesn’t suffer just because our encryption layer hit an error. But that same webhook does not get written to disk. We will not silently fall back to storing your data unencrypted just to avoid an error message. An encryption failure becomes a delivery event, not a data exposure event. That’s a deliberate tradeoff, and it’s the one we think is correct.
Hardware keys, not passwords
Staff access to our own corporate systems requires a hardware security key. Not a password, not an authenticator app, not SMS. Phishing-resistant authentication is table stakes when the thing you’re protecting is other people’s sensitive data flowing through your infrastructure every day.
Why this matters
We built HookDeploy because webhooks are infrastructure, and infrastructure that mishandles sensitive data isn’t infrastructure you can build a business on. If you’re pushing payment events, health data, auth tokens, or anything else you’d rather not see leaked, that’s exactly the traffic we designed this system around. Not as an edge case. As the default assumption.