Privacy

Access you can revoke in one command.

Giving an AI access to your machine and your servers is a real decision. We designed it so you can see exactly what it can reach, and take it away completely whenever you want.

Nothing to download.

Tsunami runs in your browser. If you want it to work on your own computer — reading a file, running a build, checking your disk — that happens through a small agent you install with one line, not a heavyweight desktop application with its own updater and telemetry.

  • One command installs, pairs and registers it as a background service
  • It runs under your user account, not as an administrator
  • Its credential is stored with owner-only permissions on your disk
  • Everything it does is written to a log file you can read
  • One command removes it entirely, including the credential
install & remove
# install
$ curl -fsSL tsunamicli.codes/agent/setup.sh | bash
  ✓ Connected. You're done.

# check on it any time
$ ~/.tsunami-agent/tsunami status
  Tsunami agent is running (pid 4058322)

# remove it completely
$ ~/.tsunami-agent/tsunami uninstall
  Tsunami agent removed from this machine.

How your credentials are held

Server keys are encrypted

The SSH key for a room is encrypted at rest. It is never sent back to your browser — you see a fingerprint, never the key.

Decrypted only in the moment

When a command needs it, the key is written to a temporary owner-only file, used, then shredded.

Contained to your project

File access is locked to that room's project root. Attempts to reach outside it are refused, including paths that try to climb out.

Deletion that actually deletes.

From your account page you can remove your account permanently. It is not a flag in a database — it erases your conversations, your private room and everything scoped to it, your licence, your API keys, your usage records and your stored memories.

The one exception is deliberate: work you posted to a shared team room stays as that team's project history, with your name replaced and your ID removed. Deleting a departing colleague's updates would erase the team's record of its own work.

  • Requires your password and a typed confirmation
  • Shows exactly what will be erased before you commit
  • Refuses to run at all if it cannot reach every store — no partial deletions
delete account
This will permanently erase:
  • • 18 private conversations (412 messages)
  • • 6 personal data stores
  • • 1 licence and 2 API keys
  • • 3 feedback items you submitted
24 project updates you posted to shared rooms stay as team history, with your name replaced by "Former member".

Twenty-five dollars a month. Unlimited use.

Every room, every advisor, every project. No token meter, no per-seat maths.