Security Overview
Security Posture
LeadRX treats security as a continuous practice, not a certification milestone. We implement defense-in-depth controls across authentication, authorization, data protection, and operational monitoring. Our security controls are validated through automated enforcement in our development and release pipelines.
Authentication
Sessions are managed through secure, HTTP-only cookies. Session tokens are hashed before storage and are never exposed to client-side JavaScript or response headers. All sessions have configurable expiry with automatic rotation. Password reset is admin-controlled in an invite-only model.
Authorization
LeadRX enforces role-based access control across five portal types: admin, staff, provider, member, and kiosk. Each tRPC procedure is classified into an explicit authorization tier (public, authenticated, tenant, admin, staff, or module-gated). Tenant isolation is enforced at the query level by scoping all data access to the authenticated organization.
Transport and Request Security
All connections are served over HTTPS. Security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy are applied to every response. API mutations are protected by origin validation and CSRF token verification.
Data Protection
Personal data is classified into five sensitivity tiers (C1 through C5) with controls proportional to classification. Sensitive columns are excluded from browser-facing API responses. Configuration surfaces enforce namespace allowlists and block secret storage. Health-adjacent workout data receives enhanced retention controls and consent tracking.
Audit and Monitoring
Privileged mutation paths use structured audit middleware, and high-risk privacy actions such as DSAR lifecycle changes, raw import preview access, export dataset access, denied sensitive access, and retention execution write durable fail-closed audit evidence with correlation IDs. Audit payloads apply PII redaction before persistence so protected data is not exposed through operational logs.
Compliance Readiness
LeadRX is designed with GDPR and NIS2-style resilience expectations as architectural anchors. We maintain living compliance artifacts including a data classification register, retention schedule, and DSAR processing system. We are working toward ISO/IEC 27001 and ISO/IEC 27701 readiness — these are targets, not current certifications.
Reporting Security Issues
If you discover a security vulnerability, please report it responsibly to security@leadrx.eu. We acknowledge reports within 2 business days and provide an initial assessment within 10 business days.
This page was last updated in May 2026. For privacy-specific information, see our Privacy Notice.