Privacy
Short version: we store the numbers GitHub already publishes, plus your member number. We never see your code, and we never keep your token.
What we store
For anyone who gets looked up (member or not): GitHub login, name, avatar, and daily contribution counts — the same numbers behind the green squares on your public GitHub profile.
For members: your member number, join date, and — once challenges ship — challenges you issue.
What we never store
Your access token: it's used once at connect time to confirm your identity, then discarded — never written to disk. Also never stored: your code, diffs, commit messages, repo names (public or private), issue or PR content, and org or teammate data. The OAuth scope we request (read:user) couldn't read most of that anyway, and we don't ask for more.
Private contributions
Private contribution counts appear on your scoreboard only because you chose to publish them on GitHub, via the “Include private contributions on my profile” setting. GitHub anonymizes them into daily totals — nobody, including us, sees which repos or what work. Turn the setting off and your published calendar shrinks; ours follows.
Deleting your data
Disconnecting deletes your membership immediately: member number, join date, badges, and any challenges you issued. Your public scoreboard page remains, like anyone's — it's built entirely from public GitHub data and would repopulate on the next lookup.
Don't want a page here at all? Ask @aparsell ↗ from the GitHub account in question (so we know it's yours) and we'll delist the login: its stored data is deleted and the page is suppressed entirely — nothing renders for it until you ask us to undo it.
No sale of data
We don't sell or share your data. There are no ads and no trackers.
Contact
scoreboard.dev is run by its owner. Questions: @aparsell on GitHub ↗. See also /terms.