Security Architecture & Threat Model
Zero Trust Client Input • Authoritative Server Computing • bodydecode.site
At BodyDecode, we do not make sensationalized marketing claims like "military-grade encryption." Instead, we implement concrete, verifiable engineering controls adhering to OWASP Top 10 web standards and strict cryptographic verification.
Client requests never supply prices or payment confirmation. The server queries authoritative prices in INR and cryptographically validates Razorpay payment signatures using timing-safe HMAC-SHA256 comparison.
Paid guides are never hosted in static public web folders. All downloads require a short-lived (15-minute) HMAC-signed token bound to an active customer entitlement record.
All incoming payment webhook events from Razorpay are verified against signing secrets and recorded with unique event IDs to prevent duplicate replay attacks and double-granting assets.
HTTP responses enforce Strict Content Security Policy (CSP), HSTS, no-sniff, and frame isolation. Server errors are sanitized to prevent stack traces or internal schema disclosure.
Vulnerability Disclosure Program
If you discover a potential security vulnerability within BodyDecode.site, please report it directly to our security engineering team at security@bodydecode.site. We will respond within 24 hours.