SECURITY
Files leave on a timer.
Signed downloads. Isolated queues. Retention you pick. GDPR-aligned handling. SOC 2 is planned, not completed.
Security overview
Convyx is built so files are isolated per account and job, travel over TLS on the public site, and leave storage when the selected retention window expires. We do not claim completed security certifications we have not finished.
File lifecycle
Upload over HTTPS, process in a bounded engine queue, store the result under an isolated object key, download through a signed URL, then hard-delete source and result objects when the job expires. The countdown starts at completion.
Encryption
Public uploads and downloads are designed for HTTPS/TLS. Production enables AES-256 server-side encryption (SSE-S3) on every object put when CONVYX_REQUIRE_S3_CREDS=1 or S3_SERVER_SIDE_ENCRYPTION=AES256. Local development may use plain HTTP to MinIO.
Infrastructure isolation
Separate image, spreadsheet, PDF, office, media, and archive queues run with per-engine concurrency and timeouts. Per-user fair-share limits prevent one account from consuming every worker slot. Objects are namespaced per user and job.
API security
API keys are scoped (convert:write, jobs:read, convert:read), optional-expiry, revocable, and hashed at rest. Plaintext is shown once. Other users' job IDs return JOB_NOT_FOUND.
Authentication
The dashboard uses session cookies. The API uses Bearer keys. Only the account that created a job can download it. Team workspaces on Business and Enterprise enforce server-side roles.
Retention
You choose retention at upload: a five-minute immediate-download grace period, 1 hour, 24 hours, or 7 days, subject to plan limits. A scheduled worker hard-deletes expired objects from storage, not just database rows.
Compliance
We operate on GDPR-aligned data handling and offer a Data Processing Addendum on request. A SOC 2 Type II audit is planned; this page will change when an engagement is formally underway. We do not claim SOC 2 today.
Incident response and disclosure
Email [email protected] with the affected route or component, impact, and reproduction steps. Do not access other users' data, degrade the service, or attach sensitive files to the first report.