← Back to Suvadu
👣

Suvadu Privacy Policy

Last updated: February 2026

TL;DR

Suvadu stores everything locally on your machine. No data is ever sent to any server. There is no telemetry, no analytics, no cloud sync, and no account required.

What Suvadu Stores

Suvadu records your shell commands in a local SQLite database. For each command, it stores:

  • The command text you typed
  • Working directory (where you ran it)
  • Timestamp (when it started and ended)
  • Duration (how long it took)
  • Exit code (success or failure)
  • Session ID (to group commands by terminal session)
  • Executor type (human, AI agent, IDE, CI/CD)
  • Tags, bookmarks, and notes you add

Where Data Lives

All data is stored locally at:

Database: ~/Library/Application Support/suvadu/history.db(macOS)
Config: ~/Library/Application Support/suvadu/config.toml(macOS)

On Linux, these are stored in ~/.config/suvadu/ and ~/.local/share/suvadu/.

What We Do NOT Collect

  • No telemetry or usage analytics
  • No crash reports
  • No command history sent to any server
  • No personal information
  • No account registration required
  • No cloud sync or backup

Network Connections

Suvadu makes exactly one type of network request:

suv update — Checks for new versions by contacting downloads.appachi.tech. No user data, command history, or identifiable information is transmitted. Only a version check.

All other commands work entirely offline. You can use Suvadu on an air-gapped machine with no internet access.

Sensitive Commands

Suvadu records all commands by default. If you run commands containing passwords, tokens, or secrets, they will be stored in the local database.

To protect sensitive data:

  • Use suv settings to add exclusion patterns (regex) that prevent recording
  • Use eval $(suv pause) to temporarily stop recording in a session
  • Use suv delete "pattern" to remove specific commands from history

Data Deletion

You have full control over your data:

  • Delete specific commands: suv delete "pattern"
  • Delete everything: Remove the database file directly
  • Full uninstall: suv uninstall removes binaries and shell hooks

Third-Party Integrations

Suvadu integrates with AI coding tools to track agent-executed commands. All integrations are purely local — no data is shared with any third party.

  • Claude Code (suv init claude-code): Installs a local PostToolUse hook that reads command metadata from Claude Code's hook events. No data is sent to Anthropic.
  • Cursor (suv init cursor): Auto-detects Cursor's integrated terminal via environment variables. Commands are captured through standard shell hooks. No data is sent to Cursor/Anysphere.

Other AI tools (VS Code, Codex, Aider, Windsurf) are auto-detected via environment variables in the shell hooks — no additional setup needed, and no data leaves your machine.

Open Source

Suvadu is open source under the MIT license. You can audit every line of code to verify these privacy claims at github.com/AppachiTech/suvadu.

Website Privacy

This page covers the Suvadu CLI tool specifically. For our website privacy policy (analytics, cookies), see the company privacy policy.

Contact

Questions about Suvadu's privacy practices? Email madhu@appachi.tech