Privacy

Short version: the cpass binary makes no network calls at all. The website and the license service handle only what's needed to sell and support a subscription.

The cpass binary: no telemetry

The only network call the cpass binary ever makes, in any command, at any point, is none. It stores your Secrets in a local, encrypted Vault on your own machine and never uploads, syncs, or transmits it or its contents anywhere. The one exception is activating a license: cpass license activate verifies a token's signature entirely offline against a public key baked into the binary — it does not call home to do so.

What claudepass.com and the license service see

• Checkout. If you provide an email on the pricing page, it prefills Stripe Checkout. Payment details are handled entirely by Stripe — we never see or store your card number.
• Subscription records. The license service keeps a minimal record tied to your Stripe customer id (a correlation id for an issued token, and subscription status) so it can issue a fresh activation command if you ever need one. It does not keep a copy of your activated license token after it's shown to you once.
• Reissue emails. If you request a new activation command via /reissue, we send it to the email address on file with your subscription.
• Server logs. Standard web server logs (method, path, status, timestamp) for operating the site and the license service — never a Secret, license token, or Vault content, because those never reach us in the first place.

Third parties

Stripe processes payment and subscription billing under its own privacy policy. SMTP delivery is used only to send reissue emails to the address already on file with your subscription.

Contact

Questions about this policy: reach out through the contact details on your Stripe receipt or subscription confirmation.