What we collect, and what we don't.

The website and docs

We measure basic traffic so we know what is useful, using privacy-first analytics:

• The marketing site (www.claw.boo) uses Cloudflare Web Analytics for page views and performance, and PostHog (US-hosted) in cookieless mode to measure which calls-to-action and features people use. PostHog's autocapture is enabled, so it records interaction events across the site (clicks, form submissions, and the text and attributes of the element you interacted with) alongside the page URL. Neither sets cookies nor stores anything in your browser, and PostHog does not identify you across sessions. Both process your IP address to serve and count requests, acting as our processors. If your browser sends a Do Not Track signal, we skip loading PostHog altogether, so no analytics request is made at all.
• The documentation (docs.claw.boo) runs on Mintlify, which provides built-in analytics. It sets no cookies, but it stores an anonymous identifier in your browser's local storage to count unique visitors, and processes standard request data such as your IP address and browser server-side.

We do not set advertising cookies, run ad pixels, do cross-site tracking, record your session, or sell data.

The Clawboo software

Clawboo is local-first. The CLI and dashboard keep all state on your own machine and upload nothing. The board lives in SQLite at ~/.clawboo/clawboo.db, and your API keys sit in an AES-256-GCM encrypted vault at ~/.clawboo/secrets/. There is no account and no product usage tracking. The only optional egress is an OpenTelemetry trace bridge you enable yourself, pointed at a collector you control.

If we add optional product telemetry in the future, we will document exactly what it collects, keep it privacy-respecting, and update this page. The source is on GitHub.

Contact

Questions about privacy: conduct@claw.boo.