Most software collects telemetry. Usage analytics, crash reports, feature tracking. For a web browser or a note-taking app, this is a reasonable trade-off — the data helps improve the product, and the risk is limited.
A terminal is different.
What Your Terminal Sees
Your terminal has access to everything that flows through it:
- Every command you type, including
ssh commands with hostnames and usernames
- Environment variables, which often contain API keys, tokens, and secrets
- Database connection strings with credentials
- Output from scripts that may contain sensitive business data
- File contents you
cat or pipe through the terminal
- Passwords entered at prompts (even if they are not echoed to the screen, the terminal processes the keystrokes)
A terminal sits at the intersection of your identity, your infrastructure, and your secrets. No other desktop application has this level of access to sensitive information in the course of normal use.
The Problem with "Anonymous" Telemetry
Terminal vendors that collect telemetry typically say it is anonymous — feature usage, session duration, crash reports. They are probably telling the truth. But there are structural issues:
- Scope creep — what is collected today may expand tomorrow. A telemetry pipeline, once built, makes it easy to add new data points.
- Metadata is data — even "anonymous" usage patterns can reveal what you work on, when you work, and how you work. Session timestamps, feature usage frequency, and connection patterns are informative.
- Network access is network access — a terminal that phones home has outbound network connections. In air-gapped or compliance-sensitive environments, any outbound connection from a developer tool is a concern.
- Trust is not verification — unless the terminal is open source and you audit the telemetry code, you are trusting the vendor's description of what is collected.
Account Requirements
Some modern terminals require you to create an account before you can use the app. This means the vendor knows who you are before you type your first command. An account ties your usage to an identity, which fundamentally changes the privacy calculus — even if the telemetry itself is "anonymous."
A terminal should not need to know who you are to let you run commands.
What Does Responsible Look Like?
We think a terminal should follow these principles:
- No telemetry by default — if you want to collect data, make it opt-in with a clear explanation of what is collected
- No account required — the core product should work without sign-up
- Local-first credentials — connection credentials should not leave the user's machine unless the user explicitly chooses to sync them
- Direct API connections — if the terminal has AI features, API requests should go directly to the provider, not through the terminal vendor's servers
- No phone-home on startup — the terminal should work fully offline
How Yaw Handles This
Yaw collects zero telemetry. It does not phone home. It does not require an account. Credentials are encrypted with AES-256-GCM and stored locally. AI requests go directly from your machine to the provider — nothing is proxied through our servers.
This is not a competitive feature. It is a baseline. We think every terminal should work this way.
What You Can Do
- Check your terminal's privacy policy and telemetry settings
- Look for opt-out options if telemetry is on by default
- Use a network monitor to see if your terminal makes unexpected connections
- Consider whether your terminal vendor needs to know who you are
- For compliance-sensitive work, prefer terminals with zero telemetry
Your terminal is one of the most privileged applications on your machine. It deserves the same scrutiny you would give to any tool that handles secrets.
Try yaw on Windows
Free, no account required. Install from PowerShell:
irm https://yaw.sh/install-win.ps1 | iex
All platforms →
Related Articles