Privacy Policy

How cmdhub handles account data, CLI usage data, provider permissions, and support requests.

Last updated: July 6, 2026.

cmdhub is operated by Stochastic Consulting Pty Ltd. Contact us at support@cmdhub.run.

This policy covers the cmdhub website, account system, billing/account features, and the cmdhub command-line tools.

What cmdhub is

cmdhub is a suite of local command-line tools for working with third-party services such as Google Workspace, Microsoft 365, Slack, and Notion. The hosted website provides account login, binary registry data, documentation, and billing/account features. The provider CLIs run locally on your machine.

Website data we store

The website stores the minimum data needed to run the service:

Data	Why it is stored
Account email, display name, login provider, provider account subject ID, and timestamps	To identify your cmdhub account and let the same identity sign in from the website and CLI.
Hashed cmdhub session tokens, session type, auth provider, expiry/revocation timestamps, and last-seen timestamps	To keep web and CLI sessions working without storing raw long-term session tokens.
Temporary CLI login handoff records	To let `cmdhub auth login` complete in the browser and return a cmdhub session token to the CLI. These records expire.
Subscription, entitlement, and billing-event metadata once paid Pro is enabled	To show account status, suppress Pro upgrade reminders for paid users, and reconcile merchant of record webhooks.
Server logs	To operate, debug, secure, and monitor the website.

Website analytics and session replay

cmdhub uses PostHog to understand how visitors use the public website and documentation, diagnose errors, and improve onboarding. This can include page views, clicks, scrolls, approximate session activity, browser/device metadata, referrer information, and limited custom events such as copying an install command or voting for a requested integration.

cmdhub may use session replay for the public website. Session replay records a reconstruction of website interactions so we can understand where users get stuck. We configure replay to mask form inputs and avoid sensitive account, authentication, API, and password-reset routes. We also avoid sending command contents, provider content, OAuth tokens, payment details, and full URLs with query strings or fragments.

Website analytics and replay data is processed by PostHog. It is used for product analytics, debugging, security, and service improvement, not for advertising or model training.

CLI data and telemetry

The CLIs send limited, opt-out telemetry so cmdhub can understand which command families are used, which commands fail, and whether installed binaries run successfully at least once.

Telemetry can include an anonymous install ID, first-run event, CLI name and version, platform, command family/action, flag names present, sanitized typed/final command shapes with values redacted, alias/rewrite diagnostics, whether arguments or piped input were present, argument count, duration, exit code, structured error code, local event time, and cmdhub account email only after a valid cmdhub CLI session is verified.

Telemetry does not include provider content, command argument values, OAuth tokens, message bodies, subjects, calendar titles, file names, file contents, Slack messages, Notion page content, full URLs, provider object IDs, local file paths, or other third-party payloads.

You can disable telemetry with:

cmdhub telemetry disable

or with CMDHUB_TELEMETRY=0, CMDHUB_TELEMETRY_DISABLE=1, or DO_NOT_TRACK=1.

Provider data and OAuth tokens

Provider app authentication is separate from cmdhub account login.

Provider OAuth happens locally: each CLI performs the provider login on your machine and stores the resulting credentials in the configured local credential backend, such as the operating system credential store where available. cmdhub does not store long-term Gmail, Google Calendar, Google Drive, Microsoft Outlook, Microsoft Calendar, Microsoft To Do, Microsoft OneDrive, Notion, or Slack provider tokens on the website.

If hosted provider token storage is introduced later, it will be optional, disclosed before use, and protected with encryption.

Data protection and security

Google Calendar, Gmail, and Drive data is requested from Google APIs by the CLI running on your machine, only to perform the command you invoked. cmdhub does not proxy Google API responses through cmdhub servers and does not store Google Calendar events, Gmail messages, Drive files, file contents, file names, or other Google provider content on cmdhub servers. Google OAuth credentials are stored locally, as described above, and telemetry does not include Google provider content, OAuth tokens, or command argument values.

Communications with cmdhub servers and Google APIs use HTTPS/TLS encryption in transit. Hosted cmdhub account, session, and telemetry records are stored in access-controlled production systems, and long-term cmdhub session tokens are stored as hashes rather than raw tokens. Access to hosted systems and telemetry records is limited to authorized operators who need it to operate, debug, secure, or support the service.

The website account system uses basic identity permissions only. These let cmdhub identify your account, display your email/name, and link the Google or Microsoft identity to the same cmdhub account.

The website Google account sign-in flow does not request Gmail, Calendar, or Drive permissions.

Provider CLI permissions

Provider CLI permissions are requested only when you connect a provider for local command-line use. Each CLI asks for the access needed to perform the commands you run, such as reading or updating mail, calendars, files, tasks, messages, pages, issues, or workspace metadata. Some CLIs also request identity or offline-access permissions so they can show the connected account and keep local CLI auth usable between sessions.

Some providers support optional, expanded permission sets for specific command families, such as Slack file workflows, Outlook shared mailbox workflows, or OneDrive shared-library workflows. Those expanded permissions are requested only when you run the corresponding login option.

Provider credentials, including OAuth refresh tokens, API keys, Personal Access Tokens, and session-style provider credentials, are stored locally by the CLI using the configured local credential backend. The current scope names and optional permission bundles are documented on each CLI integration page and are also shown by the provider consent screen during login.

Provider data is used to perform the command you ask the CLI to run. cmdhub does not sell provider content, use provider content for advertising, or use provider content to train models.

cmdhub’s use and transfer of information received from Google APIs will follow the Google API Services User Data Policy, including Limited Use requirements.

cmdhub uses service providers to operate the website and business. These can include hosting, database, email, analytics/monitoring, source hosting, and merchant of record/payment services. Provider APIs such as Google, Microsoft, Slack, and Notion receive requests only as needed to perform the commands or authentication flows you initiate.

Analytics/monitoring providers, including PostHog, may process website analytics and session replay data as service providers for cmdhub.

Payment information is handled by the selected merchant of record or payment provider. cmdhub does not store full payment card details.

Data deletion

To request deletion of website account data, hosted usage records, or support records, email support@cmdhub.run from the relevant account email.

Deletion generally covers website account records, sessions, CLI login handoff records that are still present, and hosted usage records. Some billing, tax, fraud-prevention, security, or compliance records may need to be retained by cmdhub or by the merchant of record.

You can revoke provider access directly in the relevant provider account settings, and you can remove local CLI credentials with the relevant auth logout command.

Changes

This policy will be updated as cmdhub evolves. Material changes will be reflected on this page.