Public policy
File Retention and Deletion
Normal configured windows
Browser-only tools do not send their working files to the service’s processing environment. Under the current standard configuration for server-backed tools, a completed upload that is never submitted for processing normally expires after about 30 minutes. A submitted upload remains available while its job is active and normally expires after the short configured window—currently about five minutes—runs from the last active-processing refresh. Generated output files normally expire about 10 minutes after completion. Some tool or deployment settings can differ.
Expiry and cleanup
These are expiry targets, not guarantees of deletion at an exact second or irreversible erasure from physical media. Cleanup runs periodically. Active processing or downloads, interruption, maintenance, recovery, storage errors, security needs, legal duties, or an inability to confirm safely that a file is inactive may delay cleanup. Files may be removed before a stated maximum retention period because of cancellation, capacity limits, security concerns, maintenance, or system cleanup.
Links, metadata, and recovery copies
Cancellation and expiry are intended to make a job or download unavailable through the normal service flow, while operational cleanup may finish later. Anyone with a still-valid anonymous download URL may be able to access it, so do not share that URL. Job status, security logs, operational records, caches, backups, or exceptional diagnostic copies may follow separate retention periods and may outlast the temporary file. The service does not promise that an expired file can be recovered.
What users should do
The service is not a backup, archive, or permanent-storage provider. Download results promptly and keep your own original files and backups. If you cancel an operation or need help with a deletion concern, contact us promptly with the tool, approximate time, and job identifier. Do not send the original sensitive file in the request.