Skip to content

Privacy

Tracer needs very little about you, and what it does need is listed here in full. Last updated 11 September 2026.

What is stored

From GitHub, when you sign in
Your GitHub username, display name, email address and profile picture, plus the key GitHub gives Tracer to read public information on your behalf. That key is kept so your searches count against your own GitHub allowance instead of a shared one, which is what keeps the queue fast.
What you tell Tracer about yourself
The languages, frameworks and tools you know, what you want to learn, the subjects you care about, the kinds of contribution you want, the time you have, and your experience level.
What you do here
Which issues you save, hide and open, along with the score and the technologies attached to each one. This is what lets Tracer adjust to you, and you can see all of it on your profile page rather than it being kept from you.
Public GitHub data
Projects and issues Tracer has already looked at and scored, kept for a while so it does not have to ask GitHub the same question over and over. This is public information about other people's projects, not about you.

What is not

  • No analytics, no tracking pixels, no advertising, and no scripts from anyone else.
  • Nothing from your private projects. The permission Tracer asks GitHub for covers your public profile and email address, and nothing else.
  • Nothing is ever written to your GitHub account. Tracer does not comment, assign, fork or open pull requests on your behalf.
  • No cookies beyond the single one that keeps you signed in.

Who else handles it

GitHub
Signs you in, and provides every project and issue Tracer reads.
Neon
Stores everything listed above, on Tracer's behalf.
Vercel
Runs the site itself and handles the pages your browser asks for.
OpenAI, only if the AI layer is switched on
Only when you press the button that asks for a reading of an issue. The text of that public issue and its project details are sent off to write the summary. Your profile and what you have been looking at are never sent. The feature is switched off unless whoever runs Tracer turns it on, and everything else works the same without it.

Getting rid of it

You can cut off Tracer's access at any time from your GitHub settings, under Applications. That stops it reading anything on your behalf straight away.

To have your account and everything attached to it deleted, just ask. It all goes together: your profile, your skills, your saved and hidden issues, and the record of what you have looked at.

Running your own

Tracer is open source and free to copy. If you would rather not hand anything to anyone else at all, you can run your own private copy, and none of the above applies to it.