Wraps Logo
DocsHome
Privacy

Telemetry

Wraps CLI collects anonymous usage data to help us improve the product. Your privacy is important to us.

Our Privacy Promise

We never collect personal information, domain names, AWS credentials, email content, or any data that could identify you or your users. Telemetry is completely optional and can be disabled at any time.

What We Collect

Command Usage

Which CLI commands are used and whether they succeed or fail. This helps us prioritize bug fixes and improvements.

CLI Version

The version of the Wraps CLI being used. This helps us understand adoption of new releases.

Operating System

The platform (macOS, Linux, Windows) and Node.js version. This helps us ensure compatibility.

Error Codes

When errors occur, we collect the error code (not the message) to help identify common issues.

What We Never Collect
  • Domain names or email addresses
  • AWS credentials or account IDs
  • Email content or recipient information
  • IP addresses or location data
  • Any personally identifiable information (PII)

How to Opt Out

You can disable telemetry at any time using any of these methods:

Option 1: CLI Command

Disable telemetry using the CLI:

GNU Bashterminal.sh
npx @wraps.dev/cli telemetry disable

Re-enable telemetry:

GNU Bashterminal.sh
npx @wraps.dev/cli telemetry enable
Option 2: Environment Variable

Set the Wraps-specific environment variable:

GNU Bashterminal.sh
export WRAPS_TELEMETRY_DISABLED=1

Or use the universal DO_NOT_TRACK standard:

GNU Bashterminal.sh
export DO_NOT_TRACK=1
Check Your Status

View your current telemetry settings:

GNU Bashterminal.sh
npx @wraps.dev/cli telemetry

Automatic Disabling

Telemetry is automatically disabled in certain environments to respect your privacy and avoid noise in automated pipelines:

  • CI/CD environments: Detected via common CI environment variables (CI, GITHUB_ACTIONS, GITLAB_CI, etc.)
  • DO_NOT_TRACK=1: Respects the universal Do Not Track standard
  • WRAPS_TELEMETRY_DISABLED=1: Wraps-specific opt-out

Debug Mode

Want to see exactly what telemetry data would be sent? Enable debug mode to inspect events without sending them:

GNU Bashterminal.sh
WRAPS_TELEMETRY_DEBUG=1 npx @wraps.dev/cli email init

This will print the telemetry event to the console instead of sending it, so you can verify exactly what data would be collected.

Data Storage & Retention

Where Data is Stored

Telemetry data is sent to our servers at wraps.dev and stored in aggregate form. We do not share this data with third parties.

Anonymous IDs

A random anonymous ID is generated locally and stored in your config file (~/.wraps/telemetry.json). This ID is used only to correlate events from the same installation and cannot be traced back to you.

Retention

Telemetry data is retained for 90 days in raw form, then aggregated into anonymous statistics.

Why We Collect Telemetry

As a small team building open-source tools, telemetry helps us:

  • Prioritize development: Understand which features are most used
  • Fix bugs faster: Identify common errors and their frequency
  • Improve compatibility: Know which platforms and Node.js versions to support
  • Measure adoption: Track CLI version adoption to plan deprecations

We deeply appreciate users who leave telemetry enabled. It directly helps us make Wraps better for everyone.

Related Documentation

CLI Reference

Complete reference for all Wraps CLI commands.

View CLI Docs
Getting Started

New to Wraps? Start with our quickstart guide.

Get Started

Questions About Privacy?

If you have concerns about telemetry or data privacy, we'd love to hear from you.

Contact Us