Privacy Policy
Last updated: June 2026
1. Information We Collect
When you use CommitQuest, we may collect:
- GitHub public data: username, display name, avatar, public contribution stats, language usage, stars, and repositories.
- GitHub private data (Pro only): aggregate private contribution counts — we never read code, file names, or repo names.
- Account data: GitHub login and OAuth token (stored securely in your session, never logged or shared).
2. How We Use Your Information
- To generate and display your GitHub RPG character card.
- To verify your Pro status via GitHub star check.
- To cache your card stats for performance (public cards: 6 hours, Pro cards: 5 minutes).
- To display your entry on the public leaderboard.
3. Data Storage
We store the following data in our Redis database:
- Your Pro status (a simple flag — your GitHub username mapped to a boolean).
- Your card customization preferences (title, tagline, theme, layout) — only if you save them.
- Cached GitHub stats (temporary, auto-expires).
We do not store passwords, payment card details, or private repository content.
4. Data Sharing
We do not sell, trade, or share your personal data with third parties except:
- GitHub: to fetch your contribution data via their API.
- Upstash: our Redis provider, used to store Pro status and preferences.
5. Cookies & Sessions
We use a secure, httpOnly session cookie (via NextAuth.js) to keep you signed in. No third-party tracking cookies are used. No advertising cookies are used.
6. Your Rights
You may request deletion of your data at any time by contacting us. This includes your Pro status, saved preferences, and cached stats. Your public GitHub data is controlled by GitHub directly.
7. Security
We use HTTPS, secure session handling, and server-side Pro verification to protect your data. OAuth tokens are never exposed to the client or logged.
8. Changes to This Policy
We may update this policy from time to time. The latest version will always be available at this URL.
9. Contact
For privacy-related questions, visit our FAQ page or contact us through GitHub.