Last updated: September 24, 2026. This Privacy Policy details the data handling, storage practices, and network communications of the Gmail CLI executable and documentation website.
The Gmail CLI binary contains zero tracking code, zero analytics SDKs, and zero telemetry beacons. Developer and agent terminal workflows remain 100% private. The application does not collect usage metrics, IP addresses, execution timestamps, email subjects, or error logs back to any SpaceCorps server. The only outbound network requests made by the tool are direct HTTPS calls to official Google OAuth and Gmail endpoints (googleapis.com) to fulfill user-initiated operations.
OAuth 2.0 client secrets and refresh tokens are sensitive credentials. Gmail CLI strictly refuses to save secret tokens in plain-text configuration files by default. Instead, refresh tokens and client credentials are delegated directly to the secure credential vault provided by the host operating system: macOS Keychain Services via the native security subsystem, Windows Data Protection API (DPAPI) encrypted under user-specific credentials, or the freedesktop.org Secret Service daemon via libsecret on Linux. Plaintext file fallback is only allowed with explicit opt-in (GMAIL_ALLOW_PLAINTEXT_STORE=1) and uses owner-only 0600 file permissions.
Gmail CLI never transmits your emails or mailbox metadata to any third party. All mailbox parsing, MIME building, body rendering, and search hydration occur locally in memory within your active CLI process. Downloaded attachments and drafts remain strictly under your local file system and Google account.
This documentation website is hosted as a static site on GitHub Pages. It contains no tracking scripts, no third-party cookies, and no personal data collection mechanisms. Standard web server access logs are handled directly by GitHub in accordance with GitHub's standard Privacy Statement.