Back to Help

Security and compliance

Dynafloxis Security Posture

This page summarizes the product controls currently implemented in code and the contact points for privacy, legal, and operational follow-up.

Core controls
Technical controls already implemented in the platform.
  • Organization-scoped tenancy and authorization checks
  • CSRF protection, security headers, and rate limiting
  • 2FA support for user accounts
  • Audit logging for sensitive account, billing, and support actions
  • DSAR export, deletion, and retention cleanup workflows
  • Cookie consent persistence with no non-essential tracking by default
Privacy and legal contacts
Where to send requests and escalations.

Privacy: privacy@dynafloxis.com

Legal: legal@dynafloxis.com

DPO: dpo@dynafloxis.com

Support: support@dynafloxis.com

Urgent support: urgent@dynafloxis.com

Verified Security Evidence

These are the security proof categories Dynafloxis keeps visible for release review instead of relying on broad security claims.

TLS, HSTS, and canonical HTTPS
Production traffic is pinned to HTTPS on the canonical dynafloxis.com origins with HSTS and www-to-apex redirects.
CSP, frame protection, and CORS posture
Public routes emit hardened CSP, object blocking, frame-ancestor denial, referrer policy, MIME sniffing protection, and narrow artifact-preview exceptions.
Vulnerability and dependency gates
Release gates run repository hygiene checks, dependency auditing, Trivy scanning, and checked-in vulnerability-scan evidence before promotion.
Incident response and backup restore drills
Operational evidence tracks incident response, monitoring, backup restore drills, artifact-token validation, and readiness snapshots for release review.
Cookies
Non-essential tracking is not loaded by default. Consent state is persisted in the browser.
Monitoring
Live status is available at `/status` and the ops dashboard for authenticated users.
Next step
The compliance backlog continues in the repo docs while legal sign-off and vendor registers are finalized.