Robin

Privacy Policy

Effective 20 June 2026

Robin helps you find where to contribute in Bitcoin open source. It is designed to collect as little as possible: there are no accounts, no database, and no advertising or tracking. This page explains what Robin uses and your choices. It covers both the website and the Chrome extension, which share the same backend.

What you provide

The profile you enter — languages, years of experience, interests, hours per week, your goal, and the repository you're aiming at. It is used only to generate your recommendation for that request.

Connecting GitHub (optional)

If you choose Connect GitHub, Robin uses GitHub OAuth with read-only public scope (read:user) to read your public profile and public repositories. It derives a short skill summary — your most-used languages, a few notable public repos, and your account age — and then immediately discards the access token; the token is never stored. The derived summary is kept in a secure, http-only cookie for up to 24 hours so your session works, and you can delete it any time by clicking disconnect. Robin never requests write access and never reads private repositories.

How recommendations are generated

Your profile (and the GitHub summary, if connected) is sent to Robin's server, which reads public activity for the target repository from the GitHub API and queries a large language model via OpenRouter to produce the ranked recommendations. Your data is not used to train any model.

What's stored, and where

No accounts and no database. Your most recent result is cached locally in your own browser (localStorage on the web, chrome.storage.local in the extension) so it persists between visits — you control it with “New session” or by clearing your browser/extension storage. The only server-readable item is the short-lived GitHub summary cookie described above.

Third parties

Robin relies on OpenRouter (model inference) and the GitHub API (repository signals and, if you connect, your public data). Their handling of requests is governed by their own policies.

Browser extension permissions

The extension requests only: storage (to save your last result and the backend setting), activeTab(to read the current GitHub tab's repository when you open the popup), and access to github.comand Robin's own domain (to show Robin on the GitHub page and call the API). The extension holds no secrets — all keys live on the server.

Your choices

Disconnect GitHub to delete the summary cookie. Use “New session,” or clear the site's data / the extension's storage, to remove cached results. Because there are no accounts, there is nothing else retained about you.

Changes & contact

We may update this policy; material changes will update the date above. Questions or requests: the Robin repository.

← Back to Robin