·6 min read

Zero Telemetry: Why Privacy Matters in Developer Tools

Most apps collect data about how you use them. FoxTerm doesn't. Here's why zero telemetry isn't just a feature — it's a principle.

PrivacySecurityTelemetryTrustEthics

Open almost any app on your Mac, and you'll find analytics SDKs quietly collecting data: which features you use, how long sessions last, what errors occur. For many companies, this is standard practice — "product improvement," they call it.

FoxTerm takes a different stance: zero telemetry. No analytics, no tracking, no data collection of any kind. Here's why.

What Is Telemetry?

Telemetry is automated data collection from software in use. Common types include:

  • Usage metrics — Which features are used, how often
  • Performance data — Load times, crash rates, memory usage
  • Error reports — Stack traces when things go wrong
  • Environment info — OS version, hardware specs, locale

Companies argue this data helps them improve products. And sometimes it does. But it comes with costs.

The Privacy Cost

Data Aggregation

Even "anonymous" telemetry can be deanonymized. Combine usage patterns with timestamps, IP addresses, and device fingerprints, and you can often identify individual users.

Data Retention

Collected data doesn't disappear. It's stored in databases, backed up, analyzed, and sometimes shared with third parties. You rarely control how long it's kept or who sees it.

Scope Creep

What starts as "crash reporting" often expands to "usage analytics," then "feature engagement," then "behavioral profiling." Each expansion happens without explicit consent.

Security Risk

Every dataset is a target. If telemetry servers are breached, user data is exposed. Even encrypted data can be valuable to attackers.

The Trust Cost

Developer tools handle sensitive workflows: SSH connections to production servers, database credentials, API tokens, private keys. Trust is paramount.

When a tool collects telemetry, developers ask:

  • What exactly is being collected?
  • Where is it sent?
  • Who can access it?
  • How long is it stored?
  • Can I opt out?

Answering these questions requires transparency — and many companies aren't transparent enough.

FoxTerm's Approach

FoxTerm collects zero telemetry:

  • ❌ No analytics SDKs
  • ❌ No crash reporting without explicit consent
  • ❌ No usage tracking
  • ❌ No "phone home" behavior
  • ❌ No hidden network calls

You can verify this by auditing the codebase. There are no analytics endpoints, no tracking libraries, and no data collection of any kind.

Why?

Principle: Your workflow is your business. We build tools; we don't surveil users.

Security: Fewer network calls mean fewer attack surfaces. No telemetry servers to breach, no datasets to leak.

Simplicity: Less code means fewer bugs, less maintenance, and faster development.

Trust: We'd rather earn your trust through quality than extract it through data collection.

Alternatives to Telemetry

How do we improve FoxTerm without telemetry?

Direct Feedback

We encourage users to report bugs and request features directly via email or GitHub issues. This feedback is:

  • Explicit — You choose to send it
  • Contextual — You explain what's wrong
  • Actionable — Clear steps to reproduce

Open Source Components

FoxTerm uses open-source libraries (Ghostty, libssh, libvncclient). Bugs in these components are reported and fixed upstream, where the community benefits.

Beta Testing

We release beta versions to early adopters who voluntarily provide feedback. This gives us real-world testing without covert data collection.

Crash Dumps (Opt-In)

If the app crashes, you can optionally send a crash dump. This is:

  • Manual — You choose to send it
  • One-time — Not automatic
  • Transparent — You see what's included

Industry Trends

Some companies are moving away from telemetry:

  • Signal — No telemetry, ever
  • Proton — Minimal, opt-in only
  • 1Password — Opt-in crash reporting
  • Linear — Transparent about what's collected

The tide is turning. Developers are demanding privacy-respecting tools.

What You Can Do

Audit Your Tools

Check what your apps are sending:

# Monitor outgoing connections
sudo tcpdump -i en0 port 443

# Check app entitlements
codesign -d --entitlements :- /Applications/AppName.app

Demand Transparency

Ask vendors:

  • What data do you collect?
  • Where is it sent?
  • How long is it stored?
  • Can I opt out?

If they can't answer clearly, consider alternatives.

Support Privacy-First Tools

Vote with your wallet. Support companies that respect your privacy.

The Bottom Line

Privacy isn't a feature — it's a right. Developer tools should empower you, not surveil you. FoxTerm is built on this principle, and we won't compromise it.

Download FoxTerm at foxterm.app. No telemetry, no tracking, no compromises.