Data flow & retention

Local execution, Outloop Cloud and external providers are separate data-processing boundaries.

Your Mac · Outloop + your agent

Local credentials, Workspace configuration, files, audit and browser state

Approved requests ↔ resultsConnected services

Provider APIs and websites you authorize

Task content ↔ model responsesYour AI provider

Cloud models receive the content your agent sends. Local inference runs on your hardware.

Account metadata ↔ licence / feature messagesOutloop Cloud

Accounts, billing, activation and feature-specific relays described below

Conceptual data flow, not a network-topology specification. External models and connected services are distinct from Outloop Cloud.

Credentials and model visibility

In the normal brokered API flow, credentials are stored in macOS Keychain and used on the host for the authorized provider request. Raw credential values are not returned through that flow to the agent or model. Provider responses are processed for redaction before returning to the agent.

This is not a guarantee against a compromised Mac or an operator with broad local access. Optional command integrations can expose approved credentials to a selected local process. Never paste secrets into prompts, files or support requests.

What models can receive

A cloud AI model can receive task prompts, file excerpts, returned business data and browser content that your agent sends. Redaction is not a guarantee that all personal or commercially sensitive data is removed. Browser images and audio must also be treated as potentially sensitive.

Optional model-assisted Browser Login sends sanitized page context and, where configured, the login username to the selected model provider. It is designed to exclude known passwords and authenticator codes. Review the model, account terms and enabled features before use.

What Outloop Cloud handles

Cloud handles account and onboarding information, plans, billing state, activation and licences. Operational data includes a hashed device identifier, a device label, app and OS versions, and opaque Workspace and connection identifiers with status information. Email-delivery records and configured marketing attribution are also processed. Cloud administrators can access account and operational information needed to run the service.

Normal brokered API requests go directly from the Mac to the connected provider. Outloop Cloud does not receive their request or response bodies, the agent’s prompts or outputs, or local audit records through that path. The feature-specific exceptions below have separate handling.

Feature-specific paths

Confirm availability and configuration for your deployment. These paths have different data-handling rules; they are not a promise that every feature is enabled.

Server-side OAuth exchange: connecting TikTok Ads requires Cloud to exchange an authorization code and temporarily handle access and refresh tokens before one-time delivery to the Mac. The implementation removes tokens after delivery and expires unclaimed tokens. Encryption at rest does not prevent Cloud from processing those tokens.
Reviewed cross-Mac transfer: the implementation relays a customer-encrypted package, potentially including Workspace files and credentials, to the approved destination Mac. Cloud does not hold the package decryption key. Browser Login credentials are excluded. Package cleanup and backup retention must be confirmed for your deployment.

Retention and deletion

Review each storage location separately.
Data	Location and purpose	Retention / deletion boundary
Local credentials	macOS Keychain for the normal brokered API flow. Optional transfers and sign-in exchanges have separate handling below.	Removing a Workspace grant does not delete the credential. Review Keychain, provider tokens and browser sessions separately.
Workspace files, context and browser state	On the customer-controlled Mac. An agent may send content to its selected model or connected provider.	Customer-controlled cleanup; also review backups, exports and the agent runtime’s own records.
Cloud account and operational data	Account, billing/license state, activation and limited Workspace/service metadata.	Retention criteria are described in the Privacy Policy. Removing a Mac or Workspace does not by itself erase account records. Request deletion through support.
Model and connected-service data	Providers chosen by the customer process prompts, files, API requests/results or browser content sent to them.	Their contracts, settings and retention policies apply. Deleting local or Outloop account data does not delete provider copies.

Review each storage location separately.

Local credentials

Location and purpose: macOS Keychain for the normal brokered API flow. Optional transfers and sign-in exchanges have separate handling below.
Retention / deletion boundary: Removing a Workspace grant does not delete the credential. Review Keychain, provider tokens and browser sessions separately.

Workspace files, context and browser state

Location and purpose: On the customer-controlled Mac. An agent may send content to its selected model or connected provider.
Retention / deletion boundary: Customer-controlled cleanup; also review backups, exports and the agent runtime’s own records.

Cloud account and operational data

Location and purpose: Account, billing/license state, activation and limited Workspace/service metadata.
Retention / deletion boundary: Retention criteria are described in the Privacy Policy. Removing a Mac or Workspace does not by itself erase account records. Request deletion through support.

Model and connected-service data

Location and purpose: Providers chosen by the customer process prompts, files, API requests/results or browser content sent to them.
Retention / deletion boundary: Their contracts, settings and retention policies apply. Deleting local or Outloop account data does not delete provider copies.

For retention criteria and deletion requests, see the Privacy Policy and the linked request process. This technical overview does not change the policy or introduce deletion deadlines.

Use the data deletion request process for Outloop-held data. Local data and third-party provider copies need separate action. Revoking access prevents future authorized use within its scope; it does not undo completed actions or necessarily cancel work already in flight.