Skip to content
GitVis Every contribution counts.

GitVis

Privacy

Last updated:

GitVis is built to need as little information as possible. There are no accounts, no cookies for analytics or sign-in, and no access to your repositories. This page explains what GitVis does handle, why it needs it, and for how long.

At a glance

  • No accounts or sign-in, and you never give GitVis an access token.
  • Only public contribution counts are used, never repository contents.
  • GitVis's own cache expires on its own: most of it within about a week, earlier GitHub years within 30 days.
  • Page views are counted without cookies, and identifying details are filtered out before a pageview is sent.

What GitVis does

GitVis turns public GitHub and GitLab contribution activity into a graphic for your README. You don't create an account or sign in, and GitVis never asks you for an access token or for permission to your repositories. GitHub's API requires a token, so GitVis's server uses its own; it never reaches your browser and gives no access to your account.

Public contribution data

When you enter a username in the studio, or someone views a published graphic, GitVis's server requests:

  • From GitHub: the public contribution calendar, meaning the number of contributions on each day. When a profile owner has chosen to show private contributions publicly, GitHub reports them as aggregate counts, without repository names or contents.
  • From GitLab: the public contribution calendar, the same daily counts GitLab shows on the profile, which likewise include private activity only as counts when its owner has chosen to show it.
  • A profile picture, only when the design shows one, from GitHub or GitLab. GitLab may serve it from Gravatar.

GitVis never reads repository names, code, commits, issues or other repository contents, and it doesn't request access to private repositories.

In the studio, the usernames and design choices you enter are kept in the page address, so a reload or an Edit link restores your work, and they're sent to GitVis's server to load your data. GitVis doesn't store them in cookies or browser storage.

A published image address contains your usernames and design settings, including any display name or title you typed, because that's what tells GitVis how to draw the image. Anyone who can see your README can see that address.

What's cached, and for how long

Caching lets your graphic load quickly without asking GitHub or GitLab each time it's viewed. GitVis's cache entries expire automatically: a graphic that keeps being viewed keeps getting fresh copies, and one that stops being viewed ages out.

Recent contribution counts (each platform's past year)
Up to about 7½ daysQuick images; refreshed every 12 hours when viewed
Earlier GitHub years (multi-year designs only)
Up to 30 days (the current year: 1 day)Finished years rarely change
Profile pictures
Up to 7 days, refreshed after a day when viewed. A failed lookup is remembered for 1 hour.Embedded in the image
“Account not found” results
1 hourAvoids repeated lookups

Copies outside GitVis's cache. Finished images are also kept by Vercel's network, by browsers and by GitHub's image proxy. GitVis tells them to keep an up-to-date image no later than the end of its 12-hour data window (00:00 or 12:00 UTC), but it can't guarantee how long each of them keeps a copy. Vercel's hosting logs follow Vercel's own retention.

Rate limiting. To limit abuse, GitVis counts requests per IP address in its server's memory, in one-minute windows. GitVis doesn't write these counts to storage or to its logs; they're cleared when that server instance stops, or sooner when the list fills up.

Website analytics

GitVis uses Vercel Web Analytics to count visits to its home page and studio. GitVis doesn't use cookies for analytics: Vercel tells visits apart with a hash of each request and keeps visitor sessions for no more than 24 hours. Each counted view records its page, the referring site's domain, and general details such as country, browser, operating system and device type.

Before an analytics pageview is sent, GitVis:

  • Counts only two pages: / and /studio.
  • Removes query strings and fragments from the page address, so the usernames and design settings in studio and Edit links aren't sent.
  • Keeps a referring site only as its domain, such as github.com, when that's all the browser reports. If the referrer includes a page path or query, such as a GitHub repository page, that visit isn't counted at all.

Image addresses (/api/card, /api/label) and other endpoints aren't part of analytics, and GitVis sends no custom events. Because of this filtering, the analytics deliberately undercount visits.

Hosting and other services

  • Vercel hosts GitVis. Separately from Web Analytics, and for every request including images, it processes technical request information, such as IP addresses, browser details and the addresses requested (which, for images and studio links, contain usernames), to serve the site, protect it from abuse and keep logs. See Vercel's privacy policy.
  • GitHub and GitLab supply the public contribution data and profile pictures. GitLab profile pictures may come from Gravatar. These requests come from GitVis's server, not your browser, and include the username being looked up.
  • GitHub's image proxy: when a GitVis image appears in a GitHub README, GitHub loads it through its image proxy, so GitVis receives a request from GitHub, not from the person reading the README.
  • Nothing else: fonts are bundled with the site, and its pages load no scripts, fonts or images from other websites. There are no ads and no social widgets.

Check it yourself

GitVis is open source, so every statement on this page can be checked against the code:

Contact

For privacy questions, open an issue on GitHub. Issues are public, so please don't include personal or private information. To report a security vulnerability, follow the security policy.

Changes

If GitVis changes how it handles data, this page and its date will change. Its full history is public in the repository.