> ## Documentation Index
> Fetch the complete documentation index at: https://biobase.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Where your data lives

> What stays on this device, what reaches the model, and what Infera Cloud keeps.

## On this device

Each Data Agent workspace works in a local folder, and BioBase writes the agent's outputs into it. A workspace you open from Infera Cloud without choosing a folder downloads into the BioBase folder in Documents, or into the **Data Agent workspace folder** set in Settings.

BioBase also keeps its own records in its application data folder on this device, apart from your workspace folders. These include the sync index, the conversation of each private workspace, temporary copies made while files transfer, and versions you restore with **Save a copy**.

## Backup off by default

Backup is off for every new workspace. With backup off, the workspace is private: Infera Cloud doesn't save its conversation or its workspace files. Files copied for an analysis are covered under [Where code runs](#where-code-runs). The session appears in your account with the title **Private workspace**; the real title stays on this device.

For a private workspace, Infera keeps operational records: the session's status, the timing and token counts of each run, and billing records.

## What reaches the model

The backup switch states its scope: "Nothing is saved to Infera Cloud. File contents are sent to the model to answer your question."

Each request sends your message, the recent conversation, and the contents of files the agent reads. A model provider processes these contents to produce the answer. File contents pass through Infera on their way to the model. Infera deletes these temporary copies when the turn ends, and any copy that cleanup misses expires automatically within minutes.

## Where code runs

Code the Data Agent writes runs in a cloud analysis environment. Files a step needs are copied there for that turn. In a private workspace, BioBase brings the outputs into your folder, then clears the environment.

If an output can't be brought back or clearing fails, the files stay in the analysis environment until BioBase clears them. They don't expire on their own. BioBase recovers the outputs and clears the environment before the next analysis in that workspace, and deleting the workspace also clears it. If clearing fails: "BioBase could not clear the analysis environment for this workspace. It will try again before the next analysis."

Text printed by the agent's commands is kept in the analysis environment for a short recovery window, then deleted automatically. Deletion can be delayed while the analysis service is unavailable.

## Turning backup on and off

Turning backup on uploads the workspace folder to Infera Cloud, except the [excluded files](/your-data/backup-and-sync#what-is-not-backed-up), and keeps the conversation there from the next turn.

Turning backup off pulls the cloud copy of the conversation to this device, then removes the workspace's content from Infera Cloud and returns it to private. If the removal can't reach Infera: "Infera Cloud has not yet cleared this workspace. BioBase keeps everything here and will try again when the workspace is next opened."

## Analytics

The Privacy setting states that scientific content, chat text, credentials and file contents are excluded from analytics, and that collection stops for protected sessions, which include workspaces with backup off. See [Privacy](/settings/privacy).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.