What we collect, what we don't.

The short version

• ■ The product never phones home. Daemon, CLI, MCP server, hooks — zero outbound network requests by default. No analytics, no crash reporter, no update pings.
• ■ The website uses Plausible (anonymous, aggregate, no cookies, no individual tracking) — runs always, requires no consent under GDPR/PECR.
• ■ Google Analytics 4 only loads after you click Accept on the consent banner. If you click Reject, or have Do Not Track enabled, GA4 is never fetched and no Google cookie is set.
• ■ No accounts on the marketing site. We don't ask for an email to download. Pricing checkout is handled by Stripe — see their policy below.

The product (daemon, CLI, MCP, hooks)

ClauLock's product code is local-first by structural design. The daemon binds a Unix socket scoped to your user, the vault is a local file at ~/.clsec/vault.clsec, and the keys live in mlocked memory zeroed on shutdown. There is no SaaS component, no opt-in telemetry channel, no crash reporter, no update server. We can't receive your data because there is no endpoint to receive it.

The release pipeline ships signed binaries with reproducible builds and a public SBOM so you can verify this claim end-to-end.

The website (claulock.com)

Plausible Analytics

We use Plausible, an EU-hosted, open-source analytics service that records page views and referrers in aggregate only. It uses no cookies, no localStorage, no fingerprinting; visitor IPs are hashed with a daily-rotated salt that's discarded at end of day, so sessions cannot be reconstructed. Plausible is GDPR/PECR/CCPA-compliant by design and does not require consent. It runs on every page regardless of your choice in the consent banner.

Google Analytics 4 (opt-in)

If you click Accept on the consent banner, we additionally load Google Analytics 4 (gtag.js) for richer audience and conversion insights. We configure GA4 with anonymize_ip: true, allow_google_signals: false, and allow_ad_personalization_signals: false — meaning Google should not use this data for ad personalization or cross-site profiling. Cookies set: _ga, _ga_* (Google's standard analytics IDs).

If you click Reject, gtag.js is never fetched, no Google cookie is written, and Google receives nothing. The same applies if you have your browser's Do Not Track setting enabled — we honor DNT as an absolute opt-out, even if you previously accepted.

Cloudflare (edge & security)

The site is served through Cloudflare. Cloudflare logs request metadata (IP, user agent, ASN, country) at the edge for DDoS protection and abuse prevention; per their policy, this data is retained for security purposes and not sold.

Stripe (payments)

Pricing CTAs link out to Stripe Payment Links hosted on stripe.com. We do not handle, see, or store any payment data. Stripe's data handling is governed by their privacy policy.

Self-hosted assets

Fonts (Inter), the favicon, and OG preview images are served from claulock.com directly — no Google Fonts CDN, no third-party font/image loaders. The download CTAs redirect through /download/<asset> to GitHub Releases; we keep an aggregate count of downloads per asset for capacity planning, with no per-IP retention.

Your controls

• ■ Reject the banner. No GA4 ever loads. Your decision is stored in localStorage.cl_consent; we do not read it for any other purpose.
• ■ Enable Do Not Track in your browser. We honor it as a hard opt-out: GA4 is never loaded even if you previously accepted, and the banner won't reappear.
• ■ Reopen the banner. Clear cl_consent from this site's localStorage (DevTools → Application → Local Storage) and reload. Your previous decision is forgotten and the banner shows again.
• ■ GDPR / CCPA rights. If you're in the EU/EEA, UK, or California, you have the right to access, correct, or delete personal data we hold about you. Email [email protected] and we'll respond within 30 days.

Data controller & contact

ClauLock is operated by Jesús E. Viera (San Juan, Puerto Rico, USA). For privacy questions, opt-out requests, or data subject access requests, write to [email protected]. For security issues, see /security or write to [email protected].

Material changes to this policy will be announced on the changelog.