Skip to main content
Wraps CLI collects anonymous usage data to help prioritize features, identify error patterns, and understand which platforms and versions to support. No personally identifiable information is ever collected.

​
What is collected

​
Collected

Data pointExample
Command nameemail init, sms status
Success or failuretrue / false
Command duration45000 ms
CLI version1.2.0
Operating systemdarwin, linux, win32
Node.js versionv20.10.0
Service typeemail, sms
Configuration presetstarter, production, enterprise
Error codesAWS_CREDENTIALS_INVALID (not messages)
Hosting providervercel, aws, railway, other

​
Not collected

Wraps never collects:
  • AWS account IDs or credentials
  • IAM role ARNs
  • Domain names or email addresses
  • IP addresses
  • File paths or directory structures
  • Template contents
  • Environment variables
  • Error messages (only standardized error codes)
  • Command flag values (only whether a flag was passed)
  • Any user-generated content

​
Anonymous identification

The CLI generates a random UUID the first time it runs and stores it locally. This ID is used only to aggregate usage patterns — for example, to understand the sequence of commands a typical user runs. It cannot be linked to your identity, email address, or AWS account. Config file location:
OSPath
macOS~/Library/Preferences/wraps/telemetry.json
Linux~/.config/wraps/telemetry.json
Windows%APPDATA%\wraps\Config\telemetry.json

​
How to opt out

Telemetry is enabled by default. You can disable it using any of the following methods.
Disable telemetry persistently:
wraps telemetry disable
Re-enable it:
wraps telemetry enable
Check current status:
wraps telemetry status

​
Opt-out priority

When multiple methods are configured simultaneously, they are checked in this order (highest to lowest priority):
  1. DO_NOT_TRACK=1
  2. WRAPS_TELEMETRY_DISABLED=1
  3. CI environment detection
  4. Config file setting

​
Debug mode

To inspect exactly what the CLI would send — without actually sending it — use debug mode: 
WRAPS_TELEMETRY_DEBUG=1 wraps email init
Debug mode prints the full event payload to your console and does not transmit anything to Wraps servers. Example output: 
[Telemetry Debug] Event: {
  "event": "command:email:init",
  "properties": {
    "success": true,
    "duration_ms": 1500,
    "cli_version": "1.2.0",
    "os": "darwin",
    "node_version": "v20.10.0",
    "ci": false
  },
  "anonymousId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": "2025-01-15T10:30:00.000Z"
}

​
Data retention and privacy

DataRetention
Raw events90 days
Aggregate statisticsIndefinite (no PII)
Vercel proxy logs7 days
Pipeline: CLI → Vercel API endpoint (validation + PII sanitization) → PostHog → internal analytics dashboard. All events are transmitted over HTTPS. Only Wraps team members have access to the data. Wraps does not sell, rent, or share telemetry data with third parties.

​
GDPR compliance

Wraps telemetry is designed to be GDPR-compliant:
  • Data minimization — only anonymous, operationally necessary data is collected
  • No PII — the anonymous UUID cannot identify individuals
  • Transparency — this page documents everything that is collected
  • Right to erasure — wraps telemetry disable stops all future collection
  • Right to access — wraps telemetry status shows your current configuration
  • Opt-out model — telemetry is disclosed at first run and can be disabled at any time

​
FAQ

Yes. Wraps is open source. The telemetry client is in packages/cli/src/telemetry/ and the server-side endpoint is in apps/website/api/telemetry.ts in the GitHub repository.
No. Telemetry data is used solely to improve Wraps. It is never sold, rented, or shared with third parties.
No. The UUID is randomly generated on your machine and stored locally. Wraps has no way to link it to your identity, email address, or AWS account.
No. Telemetry runs asynchronously with a 2-second timeout and fires-and-forgets — it never blocks command execution. Network errors are silently ignored. The CLI continues normally if the telemetry server is unreachable.
Run wraps telemetry status. The output shows the current state and the path to the config file:
Telemetry Status:
  Status: Disabled
  Config file: ~/.config/wraps/telemetry.json

How to opt-in:
  wraps telemetry enable
Report it immediately:The team will fix it and purge any affected data.

Build docs developers (and LLMs) love

Get started for freeTalk to us