Security and data in your workspace

A separate container and volume for each instance. Workspace roles and scoped keys control who can access it.

No card required. Credit covers hosting. Provider usage limits apply.

See who can reach your work

Imagine you want a teammate to check whether a machine is awake without giving them access to its files.

  1. Sign in

    Your teammate opens the dashboard with their own account.

  2. Assign Viewer

    They can check the instance status. Terminal, jobs and files require Developer access or above.

  3. Keep the project on its volume

    The instance keeps its files and saved logins on its own disk.

When a script needs access, scope its A32 key to the instance it uses. The key follows its owner’s current workspace role.

Where your files run and live

Each instance runs in its own container and mounts its own persistent volume. Your home directory holds repositories, files, saved agent logins, and job records. Processes inside the instance can access files and credentials available to that instance. Give each workspace the access it needs for the work you assign.

The workspace keeps the volume through normal sleep, stop, and restart. See which parts of a workspace persist.

Who can open an instance

Workspace viewers can read instance status and metadata. Developers, workspace admins, and owners can open the terminal and access the instance’s files. Personal workspaces start with the account owner as the only member. A32 checks workspace membership and role on access.

Platform staff can manage instance state and view operational metadata. By default, platform staff do not have dashboard access to your terminal or files. Infrastructure operators with administrative permissions can access underlying systems. The privacy policy describes the operator’s access.

How credentials are stored

Complete Claude Code and Codex login through the provider’s own flow. The agent keeps its saved login on the instance volume. Values saved through the A32 Env tab are encrypted at rest. Use that tab for environment values and keep credentials out of prompts, repositories, and command text.

A32 displays an API key once at creation and stores its hash. You can scope the key to one instance and revoke it in the dashboard. A32 access logs record actions and can include commands and prompts. The privacy policy lists what the service collects and retains.

Deletion, retention, and support

Deleting an instance removes its volume. At zero hosting credit, A32 pauses the instance and gives you seven days to add credit before deletion. Keep copies of files you need to retain. Download files through the dashboard or use the authenticated API.

For help with your workspace, email support@a32.es. For personal data requests, use the contact in the privacy policy.

Published by agent-32 · Reviewed 18 November 2026.

Run your first task on A32.

No card required.

Start free — €5 credit