EpicWrite is an early-stage product, and we'd rather tell you exactly how we protect your work than hide behind badges we haven't earned yet. Here's what's actually in place today.
Seven layers of protection built into every part of the platform
TLS 1.2+ with HSTS secures all data in transit, and every database connection enforces TLS. Connected integration credentials get AES-256-GCM field-level encryption, session tokens are SHA-256 hashed at-rest, third-party login tokens use state-of-the-art AEAD encryption, and account passwords are secure one-way scrypt hashes.
EpicWrite is not yet SOC 2 or ISO 27001 certified. We are building our controls to align with the SOC 2 Trust Services Criteria and GDPR from day one, and a third-party SOC 2 attestation is on our roadmap as we grow. We run today on independently operated infrastructure in a single region; multi-region redundancy arrives with our managed-cloud migration.
Your creative content is never used to train AI models. Our model provider gives a contractual no-training guarantee. All AI processing occurs within our managed environment, and content is immediately discarded after processing.
Your work is protected by daily, verified backups. We run a daily backup of the full database, check that each backup is actually restorable, and practice our recovery process instead of assuming it works.
Active defenses and continuous monitoring keep your data safe around the clock
EpicWrite sits behind an edge network with no inbound ports open to our server — every request routes through an authenticated tunnel, and edge-level DDoS mitigation and a web application firewall filter traffic before it ever reaches our infrastructure.
Security is enforced through the principle of least privilege. Secrets live in an encrypted, version-controlled secrets store — never in plaintext in code, config, or logs — and access is scoped to what each service actually needs.
Proactive security is built into our development process. Dependencies are monitored and updated regularly, pre-commit gates enforce code quality standards, and a 4-tier error classification system ensures rapid incident response. Found a security issue? We want to hear about it.
EpicWrite is not yet SOC 2 or ISO 27001 certified. We are building our controls to align with the SOC 2 Trust Services Criteria and GDPR from day one, and a third-party SOC 2 attestation is on our roadmap as we grow. We run today on independently operated infrastructure in a single region; multi-region redundancy arrives with our managed-cloud migration.
Your creative work deserves real protection, not badges we haven't earned. Start writing on a platform that's honest about where it stands.