# Files & persistent volumes

Where customer work belongs and how it should move in and out.

Status: Storage contract proposed · Transfers not enabled

## Persistent workspace
The dedicated rental is intended to preserve a customer's work during its paid term. Customer files, browser profiles and installed application state belong in that customer's encrypted workspace, not in shared host folders.

## Transfers
Upload and download APIs are planned. Require rental ownership, enforce file and account quotas, normalize paths, reject traversal and symlink escapes, and use short-lived authenticated transfer URLs. Content-type metadata is not proof that a file is safe.

## Optional ephemeral tasks
An ephemeral workspace should discard task scratch data when the task ends. Saving an output is then an explicit action into persistent customer storage. A persistent rental must not unexpectedly erase the customer's work simply because an agent exits.

## Export and cancellation
Provide an export window and communicate deletion deadlines before terminating storage. The final retention schedule is a launch requirement; no universal recovery period is promised today. Customer-requested deletion must also account for backups and preservation obligations.