Privacy Policy

Data Storage

Conversations, knowledge indexes and task files are saved by the HexClaw service you are connected to: on your device for a local service, or on the server for a self-hosted cloud service. Desktop preferences remain on your device. Switching services does not migrate data. hexagon-codes does not provide an official cloud account service that syncs or hosts this data.

API Key Security

For the local desktop service, the Sidecar saves Provider API keys in ~/.hexclaw/hexclaw.yaml, with directory permissions 0700 and file permissions 0600. Provider keys are not additionally stored in the system keychain or browser storage. A self-hosted cloud connection uses that service's Provider configuration and credentials; local configuration does not automatically sync to the cloud.

Network Communication

HexClaw communicates only with network services you configure or enable. For the content a third-party model may receive, knowledge-base text chunks, query text, and your controls, see the Third-Party AI Services & Data Notice.

Fully Offline Mode

With a local HexClaw service, local models such as Ollama, and other network integrations disabled, those tasks can run offline and model requests stay on your device. A self-hosted cloud connection still requires a network; its local runtime is on the server.

Data Collection and Tracking

We do not collect user data, track user behavior, or serve ads. HexClaw is open-source software; you may audit the code at any time to verify these commitments.

Open Source and Transparency

HexClaw is released under the Apache-2.0 license. The full source code is available on GitHub for review. We welcome community participation in code audits and contributions.