English
Download NexaAct
Trust and security

Your workspace boundaries stay yours.

NexaAct is a local desktop app, not a hosted chatbot. The product is designed around isolated app data, project-scoped permissions, OS keyring storage, user-owned remote infrastructure, and a no-data-collection stance.

Download NexaAct Read website privacy
Product boundaries

The system is designed so its control plane stays visible.

  1. 01

    Isolated App Data

    NexaAct uses a private CODEX_HOME directory under the app config path. Configuration, threads, skills, plugin cache, and runtime data never touch official OpenAI Codex CLI or desktop installs.

  2. 02

    OS Keyring Secrets

    API keys and saved account tokens use the operating system keyring. If the keyring is unavailable, saves fail — plaintext secret files are never a fallback.

  3. 03

    Scoped Permissions

    Each project defines its own workspace boundary. Default execution policy is approval-on-request. You tighten or relax per project. Cross-project access requires explicit approval.

  4. 04

    Clean Environment

    NexaAct scrubs inherited Codex profile and auth environment variables before launching the app-server. The webview uses a restrictive Content Security Policy.

  5. 05

    No User Data Collection

    NexaAct does not collect user information, workspace content, prompts, files, usage analytics, or remote-control data.

  6. 06

    User-Owned Remote Infrastructure

    Remote control is deployed to the user’s own Cloudflare account. The user prepares and controls that Cloudflare environment; NexaAct does not operate a shared remote-control cloud.

  7. 07

    Local Runtime

    The bundled app-server runs locally on your machine. Agent sessions, tool execution, and provider communication happen from your desktop.

Execution model

Local runtime. Visible actions. Conservative defaults.

The bundled app-server runs on your computer. Agent sessions, tool execution, and provider communication originate from the desktop app, while approvals keep commands and file edits visible before they land.

Review the remote-control model
runtimeLocal app-server
secretsOS keyring
defaultApproval on request
remoteUser-owned Cloudflare
FAQ

Trust, in plain terms.

Does NexaAct collect prompts, files, chats, or workspace data?

No. The NexaAct desktop app does not collect user information, workspace content, prompts, files, telemetry, or remote-control data. Consent-based website analytics are described separately in the privacy notice.

Where are API keys and saved account tokens stored?

NexaAct stores API keys and saved account tokens in the operating system keyring, such as macOS Keychain. Plaintext secret files are not used as a fallback.

Who operates NexaAct remote control infrastructure?

The user deploys and controls the remote control layer in their own Cloudflare account. NexaAct does not operate a shared remote-control cloud.