Security
You're trusting us with files you can't put just anywhere. Here's exactly how we handle that trust, end to end.
In transit
Every upload and download happens over TLS 1.3. We don't accept plaintext HTTP anywhere, including internal service calls.
At rest
Files are stored in an S3-compatible bucket with AES-256 server-side encryption. Each conversion job gets its own storage key — files are never merged into a shared namespace.
Retention & deletion
You choose retention at upload: delete immediately after conversion, after 1 hour, after 24 hours, or after 7 days. A scheduled job hard-deletes expired objects from storage, not just database references.
Access control
Download links are signed and expire. Only the account that created a job (or an org member with the right role) can access it. API keys are scoped and hashed at rest — we never store a key in plaintext.
Isolation
Conversion workers run each job in a constrained, single-purpose process with no network egress beyond the storage and queue backends it needs.
Compliance
We operate on GDPR-aligned data handling and offer a Data Processing Addendum on request. A SOC 2 Type II audit is underway for Business and Enterprise customers — status published on our trust page once complete.
Vulnerability disclosure
Found a problem? Email [email protected]. We acknowledge reports within 24 hours and don't take legal action against good-faith researchers.