Skip to main content

Security

FlowStack is built with security at every layer. This page covers our security practices and the security features available to you.

Data Encryption

At Rest

  • All data is encrypted at rest using AES-256 encryption
  • Database storage uses encrypted volumes
  • Connection credentials (OAuth tokens, API keys) are encrypted with a separate key

In Transit

  • All communication uses TLS 1.3
  • API endpoints enforce HTTPS — HTTP requests are rejected
  • Internal service communication uses mutual TLS

Authentication Security

  • Password requirements — Minimum 8 characters, must include uppercase, lowercase, and a number
  • Account lockout — After 10 failed login attempts, the account is locked for 30 minutes
  • Session management — Sessions expire after 24 hours of inactivity
  • API key security — Keys are hashed before storage, only the last 4 characters are displayed

Infrastructure

  • Hosted on enterprise-grade cloud infrastructure
  • Multi-region deployment with automatic failover
  • DDoS protection at the network edge
  • Web Application Firewall (WAF) for common attack vectors
  • Regular penetration testing by third-party security firms

Compliance

StandardStatus
SOC 2 Type IICompliant
GDPRCompliant
CCPACompliant
HIPAAAvailable on Enterprise (with BAA)

Security Features by Plan

FeatureFreeProTeamEnterprise
TLS 1.3 encryptionYesYesYesYes
AES-256 at-rest encryptionYesYesYesYes
SSO / SAMLNoNoNoYes
Audit logsNoNo30 days1 year
IP allowlistingNoNoNoYes
Custom data retentionNoNoNoYes
Dedicated infrastructureNoNoNoYes
HIPAA compliance (BAA)NoNoNoYes

Reporting Vulnerabilities

If you discover a security vulnerability, please report it responsibly:

  • Email: security@onflowstack.com
  • We acknowledge reports within 24 hours
  • We aim to resolve critical vulnerabilities within 72 hours
  • We do not pursue legal action against good-faith security researchers

Best Practices for Users

  • Use strong, unique passwords for your FlowStack account
  • Enable SSO (Enterprise) to leverage your organization's identity provider
  • Use read-only API keys when write access isn't needed
  • Rotate API keys every 90 days
  • Review audit logs regularly for unexpected activity
  • Use separate projects to isolate sensitive automations
  • Don't hardcode credentials in Code nodes — use connections or environment variables instead