Privacy & Data

This page covers what happens when you connect Hexdeck to Hexcore for multi-machine team coordination. For local-only privacy details, see Hexdeck Privacy.

Network communication

When connected to Hexcore:

• A WebSocket connection is established to the relay server
• Operator state is sent to the relay, including: active file paths, current task summaries, plan text, collision data, and session statistics
• No source code is ever transmitted — no file contents, no diffs, no environment variables

Data stored by Hexcore

• Your email and display name from Google sign-in
• Hexcore names and team membership
• Invite tokens for team links
• Operator presence data is ephemeral — it exists only while connected and is not persisted

No telemetry

Hexcore 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.

Disconnecting

You can stop relaying at any time with hex relay remove <hexcoreId>. Your Hexdeck instance continues to work exactly as before — fully offline.