Further Information

Further information See additional information how the Stripe CLI operates. ## Using with Docker A Docker image allows you to run the Stripe CLI in a container. You can set two environment variables that the CLI will use: - the related setting: the API key to use for the CLI. - the related setting: the device name for the CLI, visible in the Dashboard. Since Docker containers are ephemeral, stripe-cli login cannot be used without defining a data volume. You can use the --api-key flag instead. ## Telemetry The Stripe CLI includes a telemetry feature that collects usage data to help us improve the developer experience. This feature is enabled by default. ## What data is collected The Stripe CLI collects: - Command usage patterns (which commands are run, how often) - Error rates and types to help identify issues - Performance metrics (command execution times) - Operating system and CLI version information - If detected, the name of AI coding agents invoking the CLI (such as Claude Code, Cursor, or Cline) ## What is NOT collected We do not collect: - API keys or authentication credentials - Personal information or identifiable data - File names, paths, or source code - Command arguments or flag values - Any data from your Stripe account ## Why we collect this data Telemetry data helps us: - Prioritize which features and commands to improve - Identify and fix bugs more quickly - Understand how developers use the CLI in different environments - Optimize performance for common workflows ## How to opt out To disable telemetry, set the the related setting environment variable to 1 or true: bash # Opt out for a single session the related setting=1 stripe [command] # Opt out permanently (add to your shell profile) export the related setting=1 After opting out, the CLI will not send any telemetry data. ## License The Stripe CLI is licensed under the Apache License 2.0 and verified on GitHub as being owned by Stripe.