Privacy

Trinity Local's pitch is a privacy claim, so this page is the product page. Every sentence here is checkable against the source, which is open.

What Trinity reads

Your AI conversation transcripts, on your disk: Claude Code, Codex CLI, and Antigravity session files, plus chats the Chrome extension captures from claude.ai, chatgpt.com, and gemini.google.com. It reads them to build a local index and a lens of how you decide. All of it stays in ~/.trinity/ on your machine.

What leaves your machine

Prompt content: nothing, ever. There is no hosted service, no account, no API key, and councils dispatch through the CLI tools you already authenticated, riding your own subscriptions. The one thing Trinity can send is telemetry, and it is categorical only: labels like task type, which provider won, and whether a council completed. Never prompt text, never transcript content, never file paths.

Two properties make that a structure rather than a promise. The payload is allowlisted: a fixed set of four field names, enforced at the one place events reach the wire, so a field nobody reviewed cannot be added by accident. And the identifier rotates: the install id on your disk never leaves, and what ships is a one-way hash of it plus the current month. Two events from you in the same month share an id, so we can count how many people use Trinity. Two events a month apart do not, so nobody — including us — can assemble a picture of your work over time.

You do not have to take that on faith. Run trinity-local telemetry-show --wire and it prints the exact bytes a completed council would send, including a demonstration that a prompt field handed to the emitter is stripped before the wire. telemetry-disable turns it off; telemetry-reset-id starts a new anonymous id immediately.

What we get, and what you get. Honesty is worth more here than reassurance: today this telemetry mostly helps us, not you. It tells us whether anyone beyond the author is running Trinity and which kinds of questions people bring to a council. It does not yet come back to you as anything. It ships on by default because a tool nobody can see is a tool nobody can improve — and if that trade does not sound fair for what you get today, turning it off is one command and costs you no functionality at all.

What the models see

When you run a council, your question goes to the models you chose, through their official CLIs, under the accounts you hold with them. Their handling of it is governed by their terms, not ours. Trinity adds no middleman: there is no Trinity server between you and them.

Your data, your folder

~/.trinity/ is a documented, JSON-Schema-validated folder you can read, back up, export, or delete at any time. Deleting it deletes everything Trinity knows. There is no copy anywhere else.

This website

keepwhatworks.com is a static site on GitHub Pages. It sets no cookies, runs no analytics scripts, and collects nothing. GitHub's own infrastructure logs are governed by GitHub's privacy statement.

Questions

Open an issue on GitHub — the code is the authority this page summarizes, and if this page ever disagrees with the code, the code wins and the page gets fixed.