HEXCORE
Security

Your code never leaves your machine.

Hexcore processes activity metadata only — session status, file paths, cost data. The local daemon is open source, so you can verify this yourself.

Data access

DataDetail
Metadata we process
File pathsPaths of files read or modified
Session statusAgent label, busy/idle/blocked
Plan documentsFull plan markdown and task status
Turn previewsTruncated instruction (500 chars) and response previews (200 chars)
Cost & tokensAPI cost, model, token counts
Commit messagesMessages, SHAs, file lists
Command stringsCommand text with secrets auto-redacted
Risk signalsError rate, context usage %
Never collected
Source codeFile contents never read or transmitted
Full conversationsOnly truncated previews, never complete exchanges
Command outputstdout / stderr never leaves
Commit diffsCode changes never transmitted
Env vars & secrets.env files, API keys, credentials
Search resultsOnly query strings, never results

Plan documents may reference business logic or architecture decisions. Ensure engineers avoid including credentials directly in plans or command arguments.

Infrastructure

TransitTLS (WebSocket Secure)
AuthGoogle OAuth — no passwords stored
TokensJWT with 15-min TTL, auto-refreshed
Encryption at restAES-256-GCM for stored credentials
IsolationPer-team — no cross-customer access
Opt-inRelay enabled per project, off by default
DeletionOn request within 30 days, cascading
Request DPAView source