OpenAPI ↗

DATA & SAFETY

Memory & storage

RAM, disk and agent memory are three different things.

Proposed lifecycle policy · Sanitization implementation must be verified

Three meanings of memory

Kind Examples Does ending an agent erase it?
RAM Browser processes, application buffers A process releases memory; this is not a complete sanitization guarantee
Disk Downloads, images, browser cache, pagefile, hibernation file No
Agent memory Preferences, summaries, vector store, learned skills No; it can live on disk or in an external provider

A browser can store images and page data even when the user never presses “Download.” Screenshots, swap/pagefile, hibernation and crash dumps may create additional copies. A VM snapshot with RAM can preserve working memory too.

Proposed defaults

Keep the paid customer's workspace persistent during the rental. Offer separately selected ephemeral task storage. At reassignment, rebuild the guest and perform verified tenant-data cleanup before the next customer receives access. No cross-customer reuse of browser profiles, credentials or learned agent memory is allowed.

What reset must cover

Reset the guest disk and writable image layers, user profiles, browser caches, cookies, downloads, temp folders, pagefile/swap and hibernation artifacts. Revoke computer credentials and agent/API connections. Address snapshots, object versions, exports, recordings and backups under their own retention rules.

Encryption and deletion

Deleting a file or formatting a volume is not sufficient evidence that all SSD copies are unrecoverable. A cryptographic-erasure design needs correctly implemented encryption and deletion of every recoverable copy of the relevant keys. Provider backups, wrapping keys and recovery keys matter. Validate the method against NIST SP 800-88 Rev. 2.

External memory

If an agent sends information to an LLM, Mem0, its own database or an external storage provider, resetting the computer does not delete that external copy. The customer needs separate provider deletion controls and an accurate data-flow inventory. Agent memory should be scoped to the customer, not only to a human-readable name.