Privacy
viberank is a leaderboard, so most of what it holds is public on purpose — that is what you came here to do. This page is about the rest: what is collected that is not on display, why it exists, and how to get rid of it. Last updated 28 August 2026.
The short version: your usage figures and GitHub handle are public. Your email address and submission metadata are not, and are readable only by the server. viberank has never sent a marketing email, has no mailing list, and sells nothing to anyone.
GitHub username, display name and avatar
Identifies your row on the leaderboard and your profile page.
Usage totals from ccusage — token counts, API-equivalent cost, dates active, models and tools used
This is the leaderboard. It is the data you chose to submit.
Per-day breakdowns of the above
Powers profile charts, monthly reports and the public dataset.
League names and membership, if you join one
A league board has to name its members.
Open-to-work flag and the contact address you enter there, if you opt in
The whole point of /hire is that someone can reach you. Only shown if you switch it on.
Public means public: the leaderboard, profile pages and the open dataset are all readable without an account, and search engines index them.
Your email address from GitHub sign-in
Stored so we can reach you about your own data and, in future, about the service. Never displayed, never listed, never sold. Nothing is sent to it today.
A machine ID generated by the CLI
A random UUID created on your machine so a laptop and a desktop add up instead of overwriting each other. Not derived from your hardware, and not tied to anything outside viberank.
API tokens
Stored only as a hash, plus a short display fragment. The token itself is shown once and never again.
The raw ccusage report you submit, and file/byte counts of your session-log folder
Kept to re-check totals and catch double-counting. Counts only — never the contents of your code, prompts or transcripts.
Signing in with GitHub asks for the user:email scope, which GitHub shows you on its consent screen. As of 28 August 2026 that address is stored, in a table the public site cannot read. Before that date it was requested but discarded, so if you signed in earlier and never returned, viberank does not have it.
It is used to contact you about your own data and about the service — for example, that a feature you rely on broke. It is not used for marketing, is not shared with sponsors, and is not sold. If that ever changes, this page changes first, and anything resembling a newsletter will be opt-in with an unsubscribe link.
The address shown on /hire is separate. You type that one in yourself, it only appears if you turn the open-to-work flag on, and turning the flag off removes it.
Vercel hosts the site and provides analytics. Vercel Analytics is cookieless and aggregate — page views and referrers, not individual people.
Supabase hosts the database.
GitHub handles sign-in. viberank never sees your GitHub password.
There are no advertising trackers and no third-party analytics beyond the above. Sponsor placements, where they appear, are static — they do not track you.
You can delete individual submissions yourself at /settings/submissions.
To remove your profile and everything attached to it — submissions, daily breakdowns, stored email, tokens and submission metadata — open an issue from the GitHub account in question, or email the address in the repository. Asking from the account is what proves it is yours. Deletion is permanent and is not recoverable.
Figures already included in published aggregates — a monthly report, the blog, the open dataset — cannot be retroactively unpicked from those totals, because they are sums, not rows. Nothing in them identifies you.
viberank is open source. Every change to what is collected is a commit in the public repository, and the schema is in supabase/migrations if you would rather read it than take our word for it. Material changes to this page will be noted in the changelog.