Is my data safe and private with CueCrux?

The default answer is that your data never leaves your machine, because the default deployment has nowhere else to send it.

The free Crux Daemon runs entirely locally. The store lives on your disk, retrieval runs on your CPU, and there is no account, so there is no server-side profile of you to secure. Receipts are signed and verified locally; the tamper-check tooling (corecruxctl verify-store, offline verification of exports) works without a network connection.

Writes are never anonymous. Every connection binds to a passport and every tool call carries it, which means your own store has an identity trail: you can always establish which agent, at which trust tier, wrote what.

Deletion is a governed operation, not a hope. Scoped forget implements GDPR Article 17 with a dry-run: preview exactly what a deletion will touch, then execute it, with the operation itself on the record.

Policy enforcement does not phone home either. RCX capability tokens are self-issued locally, short-lived, scoped to tools, tenant and tier, and offline-verifiable.

Hosted features are opt-in and explicit. Pro adds hosted sync and multi-device passports; Governance adds fleet-wide controls. You choose what crosses the wire, and the credit spends that pay for hosted heavy lifts each mint a signed receipt of their own.