Back to Trust Center

Security Controls

Detailed breakdown of DMHub's technical and organizational security controls. Reviewed quarterly by engineering leadership and updated when controls change.

19 implemented1 in progressLast updated: May 2026

Encryption

Encryption at rest

All data stored in Neon Postgres and Cloudflare R2 is encrypted at rest using AES-256.

Implemented

Encryption in transit

All traffic is served over TLS 1.3. HSTS is enforced with a 1-year max-age.

Implemented

Secrets management

API keys and credentials are stored in 1Password Teams and injected via environment variables at runtime. No secrets are hardcoded.

Implemented

Integration credential encryption

Third-party integration credentials (WhatsApp tokens, Twilio keys) are encrypted at rest using AES-256-GCM before database storage.

Implemented

Access Control

Multi-factor authentication

TOTP-based 2FA available for all user accounts. Required for admin roles.

Implemented

Role-based access control (RBAC)

Granular roles: Owner, Admin, Agent, Viewer. API and UI enforce role checks on all data access.

Implemented

Single sign-on (SSO)

SAML 2.0 / OIDC SSO in development for enterprise plan customers.

In progress

Session management

Sessions expire after inactivity. Tokens are rotated on re-authentication. All sessions can be revoked by the account owner.

Implemented

Monitoring & Logging

Audit log

All administrative and data-access actions are written to an immutable audit log with actor, timestamp, and IP.

Implemented

Error monitoring

Sentry captures all server-side exceptions with full stack traces. Alerts are routed to the on-call engineer.

Implemented

Uptime monitoring

Health checks run every 60 seconds across database, cache, payments, and real-time subsystems. Status is published at /status.

Implemented

Rate limiting

Upstash Redis-backed rate limiting on all public API endpoints, authentication routes, and data-export APIs.

Implemented

Secure Development

Dependency management

Renovate Bot opens weekly PRs to update dependencies. All packages pinned to exact versions to prevent supply-chain drift.

Implemented

Static analysis

ESLint with strict TypeScript rules runs in CI. `any` types and `@ts-nocheck` are banned. Pull requests must pass before merge.

Implemented

Responsible disclosure program

Security researchers can report issues at security@dmhub.ai. See /legal/responsible-disclosure for scope and safe-harbor terms.

Implemented

Incident Response

Incident response plan

Documented runbooks for common failure modes. On-call rotation with 15-minute acknowledgment SLA.

Implemented

Breach notification

Affected users notified within 72 hours of confirmed breach, consistent with GDPR Article 33 obligations.

Implemented

Business Continuity

Database backups

Neon Postgres provides continuous WAL streaming and point-in-time recovery (PITR) with 7-day retention.

Implemented

Disaster recovery

Application is deployed globally via Vercel Edge Network. Database failover is handled automatically by Neon.

Implemented

Redundancy

Critical services (database, cache, real-time) each have independent fallback paths to prevent single points of failure.

Implemented

Questions about our security posture?

Enterprise prospects can request a completed security questionnaire (VSA/SIG/SIG Lite). Reach out and we'll respond within 2 business days.

security@dmhub.ai
Security Controls | DMHub Trust