Privacy Policy
Last Updated: October 12, 2026 • Effective Version: v1.2
All webhook payloads are encrypted at rest with AES-256 and transmitted exclusively via TLS 1.3.
Stored payloads are permanently and cryptographically purged within 3 to 30 days depending on your plan tier.
Your customer data, payloads, and financial records are NEVER used to train machine learning models.
01. Introduction & Service Scope
HookSentinel ("we", "us", or "Platform"), operating via https://www.hook-sentinel.tech, provides engineering teams with high-reliability webhook proxy routing, dead-letter queue (DLQ) buffering, and 1-click replay infrastructure.
This Privacy Policy explains how data originating from Stripe, Shopify, GitHub, Lemon Squeezy, or other third-party APIs is received, encrypted, and processed when using our platform.
02. Data Processed & Minimization
Under strict data minimization principles, HookSentinel only processes the minimum technical telemetry necessary to deliver proxying and replay services:
- Raw Webhook Payloads (Buffer): The exact raw byte stream received from external providers. Stored without re-serialization to guarantee HMAC signature verification (
stripe-signature, etc.). - HTTP Headers: Essential signature headers, timestamps, and content-type metadata required for routing and cryptographic verification.
- Delivery Telemetry: HTTP response status codes (200, 500, 504), round-trip delivery latency in milliseconds, and SHA-256 integrity checksums.
- Account Details: Name, email address, and profile image provided through GitHub OAuth for authentication.
03. Security & Encryption Standards
Because financial and mission-critical webhook data flows through our infrastructure, HookSentinel adheres to enterprise-grade security protocols:
All inbound and outbound HTTP traffic requires TLS 1.3 with strict HSTS enforcement. Insecure plaintext HTTP requests are immediately rejected.
Dead-Letter Queue disk storage and database tables are encrypted with industry-standard AES-256 algorithms.
04. Data Retention & Automatic TTL Purge
Data is never retained indefinitely. All webhook records are governed by an automated Time-To-Live (TTL) lifecycle:
- Developer (Free) Tier: 3-day automatic cryptographic purge.
- Pro & Scale Tiers: 30-day automatic cryptographic purge.
When the retention window expires, raw payload buffers are permanently and irrecoverably erased from disk. Users may also trigger immediate deletion of all stored logs via the console at any time.
05. Subprocessors
We partner exclusively with globally recognized infrastructure providers holding verified compliance certifications (SOC 2 Type II, ISO 27001):
| Provider | Service Role | Location & Security |
|---|---|---|
| Supabase / AWS | Encrypted PostgreSQL DLQ Database | EU Region (Frankfurt / Stockholm), SOC 2 |
| Vercel Inc. | Low-Latency Global Edge Ingestion Proxy | Global Distributed Edge Network |
| GitHub (Microsoft) | OAuth Developer Authentication | Global, 2FA Enforced |
06. User Rights (GDPR & CCPA)
In accordance with international privacy laws, you possess the following rights:
- The right to access and export your payload history in JSON/CSV format.
- The right to delete any or all stored webhook events with 1 click (Right to Erasure).
- The right to terminate your account and wipe all associated telemetry immediately.
07. Data Protection & Inquiries
If you have any questions regarding this Privacy Policy or your payload security, you can reach out directly via the "Feedback & Support" button on our website or through our official GitHub repository.