Privacy Policy

GitHub data we use

When you sign in with GitHub we receive your GitHub ID, username, avatar and, if GitHub shares it, your email address. We store the access and refresh tokens GitHub issues so we can read your activity when you generate a recap. The access GitReplay gets is the one GitHub shows you on its authorization screen.

To build a recap we read contribution counts, pull requests, issues, repositories you own, commit counts and repository languages for the period you choose. Private repositories are only counted when your token can read them.

Private work

Private activity appears in your recap as totals, unless you choose to reveal repository names on a share page; that can include the names of private repositories. Repository names are never drawn into a rendered video.

Public profile pages

gitreplay.club/<username> shows a summary built only from public GitHub data, without anyone signing in. Private repositories are never part of it. If you want your public profile page removed, contact us.

Self-reported edits

Premium members can correct their stats before rendering. Edited values are stored separately from the values GitHub reported, and every video and share page that uses them is labeled self-reported.

Videos, storage and rendering

Videos are rendered on Amazon Web Services and stored in private storage. They are served through short-lived signed links, not public files. The archived copy of each video is deleted automatically one year after it is created; the copy kept by the rendering service has no automatic expiry yet and is removed on request.

Sharing

Every video starts private. A share link only works after you make it public, and you can turn it private again at any time. Repository names are hidden on share pages by default, and you can set a share to expire after 30 days. A public video can be downloaded and re-shared by anyone who sees it.

Analytics and cookies

We use Google Analytics only after you accept analytics cookies; until then analytics storage stays denied. We never send your GitHub username, email, GitHub ID, video ID or share link to Google Analytics, and advertising storage is always denied. You can change your choice from the Cookies link in the footer.

Errors are reported to Sentry with cookies and secrets removed. Cloudflare protects the site and processes requests on our behalf.

Payments

Payments are processed by Stripe. We never see or store your card number; we keep a record of the purchase so Premium stays active on your account.

Deleting your data

You can delete any video from your dashboard; it disappears from your dashboard and its share link stops working. To delete your account and stored GitHub tokens, contact us. You can also revoke GitReplay's access at any time from your GitHub settings. Database backups are kept for up to about 13 months and then removed automatically.

Contact

A contact address for privacy and account requests will be published here before launch.