Enterprise-Grade Trust

Security & Compliance

How we protect your publications, reader telemetry, and business assets with modern encryption, edge architecture, and rigorous access controls.

Continuous Monitoring • TLS 1.3 • AES-256 At Rest
✶

Edge Defense & DDoS Protection

Our viewer endpoints and asset pipelines run through Cloudflare's global anycast network across 300+ cities, shielding your flipbooks from Layer 3, 4, and 7 DDoS attacks.

Φ

Rigorous Encryption Standards

All data in transit is protected using modern TLS 1.3 cryptography. Publication PDF files and generated page texture tiles are encrypted at rest using AES-256 in Cloudflare R2.

Ξ

PCI-DSS Level 1 Payments

All payment flows are processed directly through Stripe Elements and Stripe Checkout. Credit card details never touch our application servers, maintaining strict PCI-DSS compliance.

Δ

Document Access Control

Publishers can protect sensitive internal publications with passcodes, lead gates, unlisted URLs, and no-index search engine directives to prevent unauthorized discovery.

Ω

Automated SSL on Custom Domains

When you point your brand's CNAME record to Editorial3D, we automatically provision, configure, and renew an SSL/TLS certificate with zero manual certificate maintenance.

θ

Verified SMTP Routing

For custom email delivery, your SMTP credentials are encrypted in our database using authenticated AES-GCM-256 encryption with rotating server-side encryption keys.

Infrastructure & Operational Security

Editorial3D's servers run in hardened container environments on Railway with managed PostgreSQL databases featuring automatic daily backups, point-in-time recovery, and network isolation. Access to production systems is restricted to authorized engineering staff via hardware key MFA and audited connection logs.

Vulnerability Disclosure & Bug Reporting

We welcome responsible security disclosures from independent researchers. If you identify a potential security vulnerability in any Editorial3D product or service, please notify our security team at security@editorial3d.com.

Please include detailed steps to reproduce, the impacted endpoint or component, and allow us reasonable time to investigate and remediate prior to public disclosure.