Privacy Policy: How We Protect Your Data
Learn how CmdBrief collects, uses, and protects your personal data. GDPR and CCPA compliant privacy practices.
1. Introduction
CmdBrief ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit cmdbrief.com.
2. Data Controller
For GDPR purposes, the data controller is:
Email: [email protected]
3. Information We Collect
What Leaves Your Machine
The CmdBrief app and the cmdbrief.com website are separate surfaces with different data flows. This table is the short version; the sections below give the detail.
| Surface | What is sent | To whom | Control |
|---|---|---|---|
| CmdBrief app | Subscription check; redacted crash reports (error, stack trace, version). Never terminal content, prompts, or files. | cmdbrief.com; Sentry (EU region) | Always on in release builds. No usage analytics in the app. |
| Website | Page views and site events | Google Analytics; PostHog (EU Cloud) | Only after analytics consent; Global Privacy Control disables it. |
| Billing | Account, subscription, and transaction identifiers | Stripe | Required to subscribe. |
Personal Data You Provide
- Pre-launch Waitlist (historical): Email, optional name, role, current tools, workflow notes, platform, source, beta contact consent, optional product update consent, and invite status for submissions made before general availability
- Consent Records: Cookie preference choices, consent version, timestamp, browser GPC status, and a local consent identifier
- Account and Invite Data: Email, device identifier and label, account and subscription status, invite campaign delivery and redemption records, and security records such as hashed authentication tokens
- Billing and Payment-Risk Data: Stripe customer, subscription, Price, Charge, dispute, and event identifiers; subscription status and renewal time; fraud-warning, refund, dispute reason and outcome codes; Terms version; and security timestamps. CmdBrief does not receive or store full card numbers or card security codes.
Automatically Collected Information
- Usage Data: Page views, content groups, form starts, clicks, referrers, and similar site events when analytics consent is enabled
- IP Address: Processed by analytics providers with IP anonymization or privacy-preserving settings where available
- App Crash Reports: When the CmdBrief app crashes in a release build, it sends the error message, stack trace, app version, macOS version, and the diagnostic messages recorded before the crash to Sentry. Home-directory paths are removed before sending; terminal content, prompts, agent responses, repository contents, and files are never included
4. How We Use Your Information
| Purpose | Legal Basis (GDPR) |
|---|---|
| Managing pre-launch waitlist records and beta contact requests | Consent (Art. 6(1)(a)) |
| Creating and securing accounts, authenticating devices, and providing subscription access | Contract performance and legitimate interest in service security (Art. 6(1)(b), Art. 6(1)(f)) |
| Processing recurring payments, calculating tax, preventing fraud, reviewing refunds or disputes, suspending access during payment review, and maintaining financial evidence | Contract performance, legal obligation, and legitimate interests in fraud prevention and legal claims (Art. 6(1)(b), Art. 6(1)(c), Art. 6(1)(f)) |
| Sending optional product updates when you separately opt in | Consent (Art. 6(1)(a)) |
| Recording cookie and privacy choices, including GPC status | Legal obligation and legitimate interest (Art. 6(1)(c), Art. 6(1)(f)) |
| Analyzing site usage through Google Analytics and PostHog after analytics consent | Consent (Art. 6(1)(a)) |
| Diagnosing and fixing crashes in the CmdBrief app from redacted crash reports | Legitimate interest in keeping the app working (Art. 6(1)(f)) |
6. International Transfers
Your information may be transferred to countries outside your residence when service providers process data. PostHog is configured for EU Cloud and Sentry crash reports are stored in Sentry's EU region, while providers such as Google Analytics may process data internationally under safeguards including Standard Contractual Clauses (SCCs).
7. Data Retention
| Data Type | Retention Period |
|---|---|
| Pre-launch waitlist records and beta contact consent | Until deletion is requested or the records are no longer needed |
| Account, device, invite redemption, and subscription records | While the account is active and afterward only as needed for security, legal, and accounting obligations |
| Raw Stripe webhook payloads used for short-term security investigation | Up to 180 days, then redacted while compact event identifiers remain for replay protection |
| Compact fraud-warning, refund, and dispute records | 24 months, subject to any longer period required for legal claims |
| Invoices, tax, payment, and accounting records | For the statutory period required by applicable financial and tax law |
| App crash reports held by Sentry | 90 days, then deleted by Sentry |
| One-time authentication codes | Short-lived and routinely deleted after use, lockout, or expiry |
| Optional product update consent | Until you opt out or deletion is requested |
| Analytics data | Up to 26 months |
| Consent records | 3 years |
8. Your Rights (GDPR)
Access
Request a copy of your personal data
Rectification
Correct inaccurate data
Erasure
Request deletion of your data
Portability
Receive data in machine-readable format
Object
Object to processing based on legitimate interests
Withdraw Consent
Withdraw consent at any time
Authenticated account holders can delete their CmdBrief account and revoke its online sessions from the account page. For access, correction, portability, objection or opt-out, broader deletion covering waitlist or provider data, or help when self-service is not available, contact [email protected].
Deletion rights are not absolute. We may retain the minimum billing, tax, fraud-prevention, security, or legal- claim records required or permitted by law, restrict those records from ordinary product use, and explain the applicable exception in our response.
9. Security
We implement appropriate technical and organizational measures to protect your personal data, including HTTPS encryption, regular security assessments, and access controls.
CmdBrief does not collect terminal content, prompts, repository contents, or detailed native-product usage telemetry as billing or dispute evidence. We rely on Stripe purchase records plus existing account, device, authentication, and security timestamps. Website analytics remain consent-controlled as described above.
10. Contact Us
For privacy-related inquiries: