Parallax

Privacy

What leaves your machine when an agent uses Parallax, what is redacted, and what the app keeps on disk.

What leaves your machine

Every tool result is sent to your agent's model provider (Anthropic for Claude Code, OpenAI for Codex, or whichever your agent uses). That includes:

  • app logs and uncaught errors;
  • texts on the screen and in the component tree, and props;
  • screenshots;
  • network requests, state and navigation, after redaction.

Logs and errors may contain whatever your app logs: tokens, personal data, payloads. Parallax does not filter them.

Do not run it where output must not leave the machine

Do not run Parallax against an app or a build whose output must not leave the machine.

What is redacted

Redaction works by names and shapes. It is a guard, not a promise.

  • Component tree and Inspector: the value of a text field with secureTextEntry, and any prop named like a secret (password, token, otp, pin and similar), are replaced by [redacted] in the app, so they never leave it. Other texts and props are shown.
  • Network: secret headers, user info and secret parameters in URLs, credential-shaped values and secret keys in JSON bodies are removed in the app before an entry is stored. See Network, state and navigation.
  • State and navigation: secret keys are masked and route params are scrubbed.
  • Approval cards: the identifying field (a path or the start of a command) is scrubbed of obvious secrets and kept in memory only.
  • Logs and errors: not filtered.

What the Parallax hooks send

If you install the optional hooks, they send the Parallax window ids and names only, never your prompt, the agent's text, or a tool's input or output. They run on your machine and talk to the window on your machine.

What the app keeps on disk

  • approvals.json: the Decisions list, 30 days: time, agent, tool name, decision and who decided. No arguments, paths or command text.
  • activity.json: the activity list, 24 hours or 5,000 entries: tool, outcome, duration, client label. No screenshots, log text or tab.
  • A sessions index, and the window layout.
  • A run directory with a token that lets a local process talk to the Parallax core.

These files are in your user's Parallax state folder, readable only by you. Clear history in the session list removes the decision and activity files and what is in memory. Parallax does not save the text of an approval card.

What goes to Parallax

Parallax has no telemetry or usage reporting, and does not send your project, logs or screens anywhere. Diagnostics are copied to your clipboard only when you choose Copy Diagnostics… or Report a Problem…, and you read them first. Report a Problem… also opens a public issue form in your browser: check what the text contains before you submit it.

The security check of stored data (ST-2) reads the app's own storage on a simulator or emulator from the Mac, read only and only when asked. Its findings carry masked evidence, never a stored value.

On an Android emulator, Parallax pushes scrcpy-server to the emulator (/data/local/tmp) while the window shows its screen, and removes its adb forward when it stops. Nothing leaves the Mac.

The installed app may check for new versions by fetching a static update feed. That request carries no project data.

On this page