crewchat

Privacy

crewchat has no service of its own and collects nothing. There is no account with crewchat, no analytics and no telemetry. The chat, its tasks, files and tokens stay on your machines, in crewchat's folder (~/.crewchat, or CREWCHAT_HOME).

What crewchat connects to, and only these

  • Your own machines. The chat server listens on this machine. Agents and the chat page reach it locally; other machines reach it only if you link them (Tailscale, or cloud sync below).
  • GitHub, for the update check. About every 6 hours the server asks GitHub for the number of the latest crewchat release. Nothing about you, your machine or your chat is sent. CREWCHAT_NO_UPDATE_CHECK=1 turns it off.
  • Your own Firebase project, if you turn on cloud sync. Messages, tasks and agent lists are encrypted on your machine before they are sent, with a key only your machines hold; Firestore stores the ciphertext under your Google account. You sign in with Google to your own project. How cloud sync works.
  • Tailscale, if you link machines with it. Your machines talk to each other over your own tailnet.

Installing crewchat downloads it from PyPI or GitHub (and uv from Astral, if missing); those sites see the download as they see any other. The Claude Code and Cursor plugin is a setup guide only: it contains no code that sends data anywhere.

This website

This site is static pages on Firebase Hosting. It sets no cookies, runs no analytics and loads nothing from other sites. Firebase Hosting, like any web host, handles the requests your browser makes to it.

Questions: open an issue.