Privacy

Last updated 24 September 2026

What Bluet is for

Bluet keeps a product's memory (what it is for, what was decided, the rules its team wrote for agents) and gives it to the AI agents working on that product. It reads; it never writes to your repositories or tools.

The local tool (npx bluet-mcp)

Everything it reads and records stays on your machine, in ~/.bluet, unless you link it to bluet.dev.
It sends anonymous usage counts: a random install id, event and tool names, success, outcome counts (how many records a brief cited, a check's verdict), the version and operating system. Never content, questions, plans, repository or product names, file paths or tokens. Turn it off with npx bluet-mcp telemetry off, DO_NOT_TRACK=1 or BLUET_TELEMETRY=0.
If you set ANTHROPIC_API_KEY, the material it judges (pull request titles and descriptions, the files written for agents) is sent to Anthropic's API with your key.

bluet.dev

What we store: your account (through Clerk), the products you create and their memory: decisions, rules, bets, roadmap, releases, the public pages you confirm, what connected sources show, a history of changes and which agents read what. Connection tokens are encrypted (AES-256-GCM) before they are stored.
What we read, and only when you connect it: GitHub repositories you choose (read-only), PostHog projects you choose (read-only), Vercel projects (read-only), and the public websites and store listings you confirm.
Models: to judge what it reads and to write briefs, Bluet sends the relevant material (pull requests, issues, the files written for agents, the records a question concerns) to Anthropic's API. Spending is capped per workspace.
Analytics: PostHog counts how the site is used (which buttons, whether a judgment was accepted), not the text of your records.
Share links you make show only the sections you tick, to anyone with the link, until you revoke it. We count views, not viewers.
Feedback you send (the one-time survey, a rating, "what's missing") is stored with your workspace so we ask the survey only once.

Who processes it

Vercel (hosting), Supabase (the database), Clerk (sign-in), Anthropic (models), PostHog (analytics), and Composio or Bluet's own GitHub App (reading GitHub), each only for the purpose above. We do not sell data, and we do not use your memory for anything but giving it back to you and your agents.

Removing it

Deleting a product in Settings deletes everything recorded for it: its memory, proposals, findings, saves and share links. Source connections belong to your workspace and stay until you disconnect them under Sources. Revoke Bluet's access at GitHub, PostHog or Vercel at any time from their own settings. To delete your account and everything in it, or to ask anything about this page, open an issue at github.com/bluet-dev/bluet-plugin.