Skip to content

What is and is not protected

A summary of the safety notes. The full text, with every detail, is in the Safety docs.

Your data

Protected

  • No accounts, no cloud sync, no telemetry. A case is a folder of Markdown files on your machine.
  • Autosave writes about a second after you stop typing.

Not protected

  • The browser build keeps cases in browser storage, without history, backups, encryption, page capture or tool running.

History and backups (desktop)

Protected

  • Version history stores snapshots of the case’s Markdown files and layout, with diff and restore.
  • Rotating automatic .zip backups of the whole case, evidence included, only when the case changed.

Not protected

  • Evidence files are not touched when you restore a version.
  • Removing a case permanently also removes its history and backups.

Encryption (desktop)

Protected

  • A locked case is stored as an encrypted file (scrypt key derivation, AES-256-GCM) and the plain folder, history and backups are removed.
  • The encrypted file is read back and verified before anything is deleted. Passphrases under 10 characters are refused.

Not protected

  • There is no recovery. If you lose the passphrase, the data is gone.
  • While a case is unlocked it is an ordinary folder, readable by anything on your computer.
  • The case id (folder name) stays visible. If the app is killed while a case is unlocked, the plain folder remains.
  • The MCP server cannot read locked cases.

Network (desktop)

Protected

  • Tools, page capture, API requests and Wayback lookups can be routed through Tor or a SOCKS/HTTP proxy.
  • If the proxy is unreachable, nothing falls back to a direct connection. DNS-only tools are blocked while a proxy is on unless you allow them.
  • Page capture runs in a sandboxed hidden window with its own in-memory session, and WebRTC address leaks are disabled.

Not protected

  • DNSRecon and dnstwist send raw DNS queries and are not routed through the proxy. The update check is not routed either.
  • Routing hides your IP address from the sites you contact. It does not make you anonymous by itself.

API keys (desktop)

Protected

  • Keys are stored encrypted with the operating-system keychain, never written into a case and not shown again.
  • If the system offers no secure storage, keys are refused rather than stored in plain text.

Not protected

  • On macOS the first save or use may show a Keychain prompt because the app is not signed with a developer certificate.

AI agents (MCP)

Protected

  • The built-in MCP server is read-only and off by default. It has no tool that changes a case.
  • It only reads Markdown files inside the workspace’s projects folder and skips symlinks and oversized files.

Not protected

  • Anything an agent reads leaves Trace through that agent. Only enable it for agents you trust with the case.

The app itself

Protected

  • The source is MIT licensed and on GitHub.

Not protected

  • Trace is alpha software.
  • Builds are unsigned (macOS ad-hoc), so your OS warns on first launch. Verify the SHA-256 from the download page.
  • There is no auto-update yet.

Report a vulnerability

Please report security problems privately through a GitHub Security Advisory instead of a public issue. Include the version, your platform and the steps to reproduce.

Open a private advisory