Data handling

Data Jio handles

A session can contain source code, repositories, shell commands, files, stdout, stderr, and credentials you explicitly transfer. The host administrator can access guest memory, files, commands, and output.

Retention and deletion

• Disconnecting does not delete a session.
• stop retains files on endpoints that support it.
• destroy permanently deletes the VM and its retained files.
• Expired hosted sessions are cleaned up according to operator policy.

Confirm the operator's retention and backup policy before using Jio with sensitive data.

Credentials

• jio login stores the API key under ~/.jio with owner-only permissions.
• JIO_API_KEY overrides the saved key and is readable by processes with access to that environment.
• VM access uses local SSH credentials generated on the client machine.
• jio login codex explicitly copies the local Codex login into the selected VM.
• Reusable runtime templates must never contain user secrets or clone-shared identity material.

Do not print credentials, pass them through logs, or commit them to a repository. Use separate, least-privilege accounts for automation when available.