We treat security as a product requirement, not an afterthought. Every architectural decision at Seraph is made with your data's confidentiality, integrity, and availability in mind.
We implement the same security standards used by regulated industries — so you can audit with confidence.
Seraph is actively pursuing SOC 2 Type II certification. Our controls covering security, availability, and confidentiality are audited annually by an independent third-party assessor. Certification expected Q4 2026.
In progress — Q4 2026All data transmitted between your browser and Seraph's servers is encrypted using TLS 1.3, the latest and most secure transport layer protocol. We enforce HTTPS across all endpoints — there are no unencrypted fallbacks.
Always-onAll data stored in Seraph's databases and object storage is encrypted at rest using AES-256. Encryption keys are managed through AWS Key Management Service (KMS) with automatic annual rotation.
Military-gradeAccess to Seraph's internal systems is governed by least-privilege RBAC. Engineers only have access to the systems they need. All production access is logged, reviewed quarterly, and requires MFA.
Least-privilegeSeraph is designed for high availability with redundant infrastructure across multiple AWS availability zones. We maintain a public status page and notify affected customers proactively during any service degradation.
Multi-AZ redundancyWe support data subject access requests, right-to-erasure, and data portability. Our Data Processing Agreement (DPA) is available for customers who require it for GDPR compliance. Contact us at privacy@seraph.ai.
EU & California readySeraph runs on Amazon Web Services (AWS) in the us-east-1 region with failover capacity in us-west-2. Our application tier, database layer, and storage are all deployed across multiple Availability Zones to eliminate single points of failure.
Database backups are performed continuously with point-in-time recovery enabled, and full snapshots are retained for 30 days. All backups are encrypted and stored in a separate AWS account to protect against accidental deletion or account compromise.
Our CI/CD pipeline includes automated security scanning (SAST, dependency vulnerability checks) on every code merge. Infrastructure changes are reviewed by at least two engineers before deployment, and all production changes are logged in an immutable audit trail.
We take security reports seriously and appreciate the time researchers invest in disclosing vulnerabilities responsibly. If you believe you've discovered a security issue in the Seraph platform, please follow these steps: