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

# Data and permissions

> Understand local app state, connected services, agent processing, and the different permission controls across Gatetrix.

Gatetrix's Mac apps keep their application state on your Mac. Work can still
involve external services when you connect a provider, use an agent, or load
public data.

## Where processing happens

| Activity | What is involved |
| - | - |
| Access calls a connected service | Access sends the approved request to that service. A calling agent receives the operation's result. |
| d0 loads public data | The host requests data from the public hosts and paths declared by the trusted dashboard. |
| d0 uses business data | The host calls tools through its configured Access profile. |
| An MTS teammate works on a task | MTS uses the connected Codex runtime and account. Prompts and tool results used by the agent can be processed by its provider. |
| MTS transcribes a recording | Audio is streamed to OpenAI. Dictation is not offline transcription. |

Read [Privacy and data collection](/privacy) for app telemetry, update requests,
and submitted feedback. The [Gatetrix Privacy Policy](https://gatetrix.ai/privacy/)
covers the broader details and service providers.

## Credentials and content are different

Access stores connector credentials in macOS Keychain and uses them when making
authorized requests. Keeping those credentials out of an agent's prompt does
not mean the data returned by a tool stays out of that agent's context.

Choose both the operations and the data sources the agent actually needs. Reading
one selected project is a different scope from reading an entire account.

## Each permission control has a purpose

* **Access profiles** determine which resources and operations are available
  through Access. Configuration Mode separately controls delegated setup.
* **d0 Agent editing** controls builder access. Trusting a dashboard version
  separately permits that version to use its declared runtime capabilities.
* **MTS allowed actions** control project data and workflow operations. A
  teammate's execution access separately controls its coding environment.

These controls apply to their respective interfaces. An agent that also has
independent shell, filesystem, or service access may have capabilities outside
Gatetrix. In MTS, review execution access as well as allowed MTS actions.

Access is not a sandbox. Its software permission checks can contain bugs, and
it does not constrain an agent's independent access. See the
[Access security model](/access/security-model).

For practical setup, see [Access permissions](/access/permissions),
[d0 runtime permissions](/d0/runtime), and [MTS connections](/mts/connections).


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