Data and permissions

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

Read Privacy and data collection for app telemetry, update requests, and submitted feedback. The Gatetrix Privacy Policy 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. For practical setup, see Access permissions, d0 runtime permissions, and MTS connections.