Last updated: September 24, 2026. This Privacy Policy details the data handling, storage practices, and network communications of the YouTube CLI executable and documentation website.
The YouTube CLI binary contains zero tracking code, zero analytics SDKs, and zero telemetry beacons. We believe developer and agent terminal workflows must remain completely private. The application does not collect usage metrics, IP addresses, search queries, execution timestamps, or error reports back to any SpaceCorps server. The only network requests made by the tool are outbound HTTPS requests made directly to the official Apify API endpoint (https://api.apify.com/v2/) to fulfill user-initiated commands.
Apify authentication tokens and API keys are sensitive secrets. YouTube CLI strictly refuses to save secret tokens in plain-text configuration files by default. Instead, API keys are delegated directly to the secure credential store 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.
Non-sensitive configuration metadata—specifically account alias names, identity labels (such as your Apify username), and plan information returned by the API—is stored locally in an owner-restricted YAML file (chmod 0600 on POSIX platforms) located within your standard system configuration directory (~/Library/Application Support/youtube-cli on macOS, ~/.config/youtube-cli on Linux, or %APPDATA%\youtube-cli on Windows). This file can be inspected, backed up, or deleted at any time.
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.