Data lifecycle
Distinguish temporary browser state, retained management records, and outputs stored by your application.
| Data | Lifecycle |
|---|---|
| Live pages, in-memory state, session cookies | Belong to the running browser and are not recoverable after it is lost |
| Uploaded and downloaded session files | Available only through a ready, unexpired session; retrieve before closing |
| Session state, timestamps, ownership, and usage records | Can remain after browser release for management and billing |
| Agent outputs, screenshots, and business logs | Store and protect in your application; no long-term platform hosting |
| Cross-session Profile state | Encrypted Cookie/localStorage snapshots retained until Profile deletion; metadata APIs expose no state values |
Plan output retrieval before cleanup
Validate and save required results before closing the session. A retained session ID cannot be used later to restore a destroyed browser or retrieve its temporary downloads.
Avoid sensitive personal data in metadata. Use application identifiers that can be correlated in your own system.
Deletion and retention commitments
Browser release and deletion of all account or billing records are different operations. A fixed public metadata-retention period, account-data deletion process, and contractual data-residency commitment have not yet been published.
If your workflow requires those commitments, obtain them from the operator before sending the relevant data. Choosing a browser region alone does not establish where every control-plane or payment record is stored.
Exported state
If your application exports website cookies or browser storage through a browser client, treat that data as credentials. You own access control, storage protection, retention, expiry, and restoration behavior.