How We Handle Files
This page explains the technical flow from upload to deletion, including what is and is not logged.
Encryption and transport
All browser-to-platform traffic is served over HTTPS/TLS.
Uploads and downloads are transmitted through encrypted channels in transit.
Temporary storage and job isolation
Each conversion job writes files into an isolated temporary job directory.
Generated outputs are linked to that job and removed automatically at expiration or manual delete.
What is logged
We log technical metadata needed for reliability and abuse prevention: tool slug, size totals, timestamps, status, and error messages.
Security controls also use hashed network and user-agent identifiers plus a device cookie identifier.
We do not index file content in public search, do not sell uploaded data, and do not use uploaded files for model training.
Anti-abuse controls
Rate limits are enforced per plan, device, and network to protect service quality.
Suspicious repeated failures can trigger temporary throttling windows.
Need per-plan timing details? Open the Retention page.