privacy

The c0mputeCLI generates a local identity key and registers a CoinPay DID. Public DIDs, signed job receipts, and worker reputation are visible to the network — that's the point.

Private keys, raw input data, and per-job logs stay on your machine unless you explicitly opt in (e.g. --report flags on doctor / crash dumps).

• No tracking pixels on this website. No third-party analytics scripts.
• No CLI telemetry by default.
• No long-lived bearer tokens — auth is signed-request envelopes per DIP-0007.

When you submit a job, its manifest (workload type, input hash, runtime image, max price) and the resulting receipt are visible to workers and validators. The actual input/output bytes are content-addressed and only fetched by parties involved in the job. For private workloads, encrypt inputs client-side; the c0mpute private trust tier (per the v1 PRD) supports this flow.

c0mpute.com uses session cookies only when you sign in to the dashboard (once that exists). No advertising cookies.

Privacy concerns: privacy@c0mpute.com