Coders Talk stores as little as it can. What you send stays private until you publish it, and what you send to a team stays with the team.

What we store

Your GitHub profile when you sign in: GitHub user id, username, name, avatar, bio and website. We never see your GitHub password and ask for read-only profile and email scopes.
What you publish: Builds, moments, comments, votes, saves and replicas.
Private Builds: every session you send or import is kept as a Build in your My builds, visible only to you, until you publish it or delete it. It is not in the feed, search engines, the sitemap or your profile.
Team Builds: a session sent to a team is visible to that team only, as its settings say (see Teams below).
Transcripts you import, only after our secret scanner has replaced keys, tokens and connection strings with [REDACTED:TYPE]. The unredacted original is not kept. A possible secret you have not decided on yet is kept encrypted so you can mark it "not a secret"; after 30 days it stays redacted for good and the encrypted value is deleted.
Plugin tokens you create in Settings: a name, a hash of the token (never the token itself) and when it was last used.
Token counts: how many tokens a session spent per model, counted on your machine from the session file by the plugin or the import page. Only the numbers.
Code changes in a session: the diffs of the files that changed, from the agent’s edits in the session or from the Claude Code plugin’s git snapshots, which also mark what you changed by hand between the agent’s answers and the commits made in each turn (hash and title). Kept with the transcript. Env, key and credential files are kept by name only. Deleted with the Build.
Git context an agent plugin sends with a session: the branch, the start and end commit hashes, the titles, hashes and size of the commits made, and the GitHub address, not the commits themselves. The address of a repository GitHub does not confirm as public is never linked: it is shown only to the Build's own audience (you, or your team) and deleted when the Build is published.
Your email, if you subscribe to the digest or add one for notifications. Digest subscriptions are double opt-in; unconfirmed addresses are deleted after 7 days.

Teams

A team is a space an organisation sets up on Coders Talk. The organisation decides what happens to its team's Builds; for those, it is responsible for the data and we process it on its behalf.

What goes to a team: sessions you send from repositories of the GitHub organisations the team named, and sessions you move or send to the team yourself. Nothing else: your private Builds and sessions from other repositories stay yours.
Before you join, the invitation page shows what the team will see; joining records that you agreed.
Automatic sending happens only if you turn on auto mode in the plugin on your computer. A team can ask for it; it cannot switch it on for you.
Who sees team Builds is the team's setting: every member, or the team's owners and admins only. The same goes for raw session logs.
If you leave a team, your Builds there stay with the team and you lose access to them. If you delete your account, they stay with the team without your name, and any that were public are taken off the site.
An owner can delete the team, which deletes every Build in it.

Private and team Builds are not shown in the site's moderation tools. We look at them only when you or your team ask us to, or when the law requires it.

Cookies and analytics

We use one session cookie to keep you signed in and a CSRF cookie to protect forms. Analytics run on Plausible, which does not use cookies or collect personal data. There is no advertising and no tracking pixels.

Who processes data for us

Hosting and database: Hetzner, Germany. Cloudflare sits in front of the site.
Email delivery: our transactional email provider (Resend or Postmark).
Import: the text of a transcript you import, after redaction, is sent to Anthropic's API to propose moments. It is not used to train models under Anthropic's API terms.
Error monitoring: Sentry. Secrets are filtered out of error reports.

Your choices

Keep a Build private, publish it, unpublish it, or delete it. Hide the raw transcript of any Build. A deleted transcript is removed from storage within 24 hours.
Leave a team at any time from the team's page.
Delete your account in Settings. This deletes your Builds, transcripts, votes, saves and replicas. Comments you left on other people's Builds stay, without your name, and so do Builds you made in a team, as described above.
Unsubscribe from the digest with the link in any issue.

Contact

Questions or requests: privacy@coders.talk.