The short version
WrapYourGit reads activity counts from GitHub to build yearly recaps. Anyone can open a recap of any GitHub username, built from public activity only, the same activity a GitHub profile shows. It never reads code, stores only what a recap needs, lets you hide your public recap, and deletes everything when you ask.
What we collect
- Your GitHub identity: numeric account id, login, display name and avatar URL, so we know whose recap is whose.
- GitHub access tokens: issued when you sign in, encrypted at rest with AES-256-GCM and used only on our server. They are never sent to your browser.
- Your recap: counts computed from your GitHub activity for the year, such as contributions per day, languages, the repositories you committed to, pull requests, issues, reviews and stars. Private repositories count toward these numbers, and a count never names a repository. Their names never appear on your public page or its card. Your own story and the files you download show them only if you choose to, and you can change that in Settings.
- Repository metadata, only if you choose: if you install WrapYourGit on your account or an organisation to count private repositories you own, it reads the metadata of the repositories you select (name, visibility, language, stars). Never their code. Your public page and its card still never show private names.
- Your private names choice: whether you chose to show private repository names in your own story and files, so we ask only once. You can change it in Settings.
- Your timezone: the one your browser reports when you sync, so the recap's dates and hours match your day.
- A session: we store a SHA-256 hash of your session token, never the token itself.
- Public recaps, for any username: when someone opens /username, we read that account's public activity with our own read-only token and store the public recap and last year's public activity (for the comparison), keyed by the account's numeric GitHub id, to answer the next visit. We read it again when it is more than 12 hours old. No sign-in is involved, and private activity is never read.
- A hashed address, for the lookup limit: each visitor can start 20 new lookups an hour. To count them we store a salted SHA-256 hash of the visitor's IP address with the time, never the address itself. Each row is kept about an hour: rows older than that are deleted, for every address, with the next lookup anyone makes.
- A check that you are a person: before we read a recap from GitHub that nobody has opened lately, a visitor who is not signed in passes Cloudflare Turnstile. On that page Cloudflare sees your IP address and details of your browser, and we send it your address with the result to confirm. We keep none of it: you get a cookie that lasts an hour and says only that the check was passed.
- Page views: Cloudflare Web Analytics counts visits to each page and how fast it loaded. Your browser sends the page's address, the page you came from, and its load timings; Cloudflare adds your country and browser type. It sets no cookies, stores nothing in your browser and does not fingerprint you, so a visit is never tied to you or your GitHub account.
- Your hide choice: if you hide your public recap, we keep your numeric GitHub id on a list, so the recap stays hidden even if you rename your account.
What we never collect
- Source code. Signing in asks GitHub for no repository permissions, and the optional installation asks for metadata only.
- Your email address, your followers or anything outside your year's activity.
- Advertising data, or anything that follows you to other sites. The only analytics are the cookieless page views above, and the site sets no tracking cookies.
How we use it
Only to build, show and export recaps: the story, the letter, the video, the slides (as PNG images or one ZIP) and the PDF, all made in your browser, and the public recap at /username. We do not sell or rent your data and do not use it to train models.
What goes public
Every GitHub username has a public recap at /username, open to anyone. It is built from public activity only, read with our token rather than yours, and shows a reduced copy:
- Private repository names and details are removed. Their commit counts still show, without a name.
- Your timezone is replaced with UTC.
- The hours of the day you commit are withheld, including the night-time share behind the Night owl archetype.
Turning on Hide my public recap in Settings takes it down immediately and deletes the stored copy. Visitors then read that you hid it. Your own story, when you are signed in, is never shown to anyone else.
Who else is involved
GitHub, whose API we read your activity from under its own privacy statement. Cloudflare, whose Turnstile widget runs the check that you are a person and whose Web Analytics counts page views, under its own privacy policy. Vercel also hosts the site, and its server code runs in Singapore. Your account, recap, tokens and sessions are stored in a Postgres database at Neon, also in Singapore. A nightly backup of that database is kept in a private, encrypted Amazon S3 bucket, also in Singapore. Cloudflare answers the site's DNS and sees no recap data. Each works under its own privacy policy.
How long we keep it
- Your recap and tokens: until you delete your data.
- Database backups: 14 days, then deleted. Data you delete leaves the live database at once and the last backup that holds it within 14 days.
- Public recaps: until the owner hides theirs or deletes their data. A stored recap is read again from GitHub when it is more than 12 hours old. While GitHub is busy, a copy up to 7 days old may be shown in the meantime, never an older one.
- Hashed addresses for the lookup limit: about an hour, deleted with the next lookup after that.
- Your hide choice: until you turn it off. It stays after you delete your data, so your public recap stays hidden.
- Sessions: 30 days, or until you sign out.
- The check that you are a person: one hour, in a cookie in your browser only.
- Page views: as counts in Cloudflare's dashboard, for as long as Cloudflare keeps them, with nothing that identifies a visitor.
- Server logs: error summaries only, without tokens or recap content.
Your choices
- Delete my data in Settings removes your account, recap, tokens and sessions, hides and deletes your public recap, and revokes WrapYourGit's access to GitHub. Backups taken before that are deleted within 14 days.
- You can also revoke access at any time on GitHub, under Settings, Applications.
- Hide my public recap in Settings, whenever you like. Turn it off again to make it public.
Changes
If what we collect or how we use it changes, this page changes first, with a new date at the top.

