HEXCORE
Docs

Privacy & Data

Hexdeck is 100% offline. Here's a complete breakdown of what it accesses.

Hexdeck makes zero network requests

The CLI and dashboard make zero network requests. No data leaves your machine — ever. There is no phone-home, no analytics endpoint, no update check, nothing. Your data stays on your filesystem and nowhere else.

The only time Hexdeck communicates over the network is if you explicitly choose to connect to Hexcore via hex relay. Without that step, Hexdeck is a fully offline tool.

How Hexdeck discovers operator activity

Hexdeck works by reading operator session transcripts — the JSONL log files that tools like Claude Code write to ~/.claude/projects/. From these transcripts, Hexdeck extracts:

  • File paths referenced in tool calls (Read, Write, Edit, etc.)
  • Operator intent — what each operator is working on
  • Session metadata — which projects have active sessions

Hexdeck does not watch your project directory or use filesystem monitoring. It only reads the session transcript files.

What Hexdeck does NOT access

  • Your source files — Hexdeck never opens or reads files in your project directory directly
  • Environment variables — .env files and secrets are never accessed by Hexdeck
  • Git credentials — authentication tokens are not touched

Note: The session transcripts Hexdeck reads may contain file contents that were recorded as part of tool results during an operator session. Hexdeck processes these transcripts to extract file paths and intent but does not index or store the file contents themselves.

What Hexdeck writes locally

Hexdeck stores minimal state on your machine:

  • PID file at ~/.hexdeck/server.pid — tracks the running server process
  • Config at ~/.hexdeck/ — stores relay connection settings, operator labels, and other preferences

If you use the menu bar app, it also stores standard macOS app data in:

  • ~/Library/Application Support/dev.hexdeck.menubar
  • ~/Library/Caches/dev.hexdeck.menubar

No telemetry

Hexdeck does not collect analytics, usage metrics, or telemetry of any kind. There are no tracking scripts, no phone-home behavior, and no third-party data collection.

For cloud-specific privacy details (what data is sent when you connect to Hexcore), see Hexcore Privacy.

CLI Commands