File retention is explicit rather than hidden. Workflows can request the supported immediate/short-lived retention policies allowed by the plan, and applications should choose the shortest lifetime compatible with their delivery workflow.
Retention modes
Source and output Files have expiry metadata and object-storage lifecycle cleanup. Signed download links expire separately from the durable File, so URL expiry never proves that the underlying File has already been deleted.
Temporary data
Worker-local intermediates are deleted at task completion. Multi-step routes keep intermediates local when safe to avoid unnecessary object-storage traffic. Temporary execution storage is not a hidden long-term archive.
Metadata
Deletion removes file payloads. Minimal usage/audit records may remain for billing, security and operational integrity without retaining the underlying document or media. Resource metadata and commercial records can therefore outlive the binary itself.
Production policy
Set retention deliberately for regulated or sensitive workloads, download outputs promptly and delete Files explicitly when early deletion matters. Treat signed download URLs as bearer capabilities: keep them short-lived and do not publish them into long-lived logs.