Your Code, Your Stats,
Zero Tracking
We believe developers should never have to surrender OAuth tokens, grant private repository permissions, or be tracked across the web just to create an aesthetic stats card.
How Your Data Actually Flows
Notice there is no intermediary backend database anywhere in the pipeline:
You enter a public GitHub username in the generator input bar. No cookie or authentication token is attached.
Your browser queries GitHub's official REST API directly from your network. Zero requests touch any private analytics server.
Stats are computed in volatile tab memory and rendered to 4K Canvas. When you close the tab, all data vanishes.
Data Collection Matrix
| Telemetry Item | Processed? | Storage Location | Retention |
|---|---|---|---|
| Public Username & Avatar | ✓ Yes | Local tab RAM only | Session (Discarded on close) |
| Public Stars & Repos | ✓ Yes | Local tab RAM only | Session (Discarded on close) |
| Theme Preference (Dark/Light) | ✓ Yes | Browser localStorage | Persistent until cleared |
| GitHub Passwords & OAuth | ✕ NEVER | Not accessible | None (Zero access) |
| Private Repos & Commits | ✕ NEVER | Not accessible | None (Zero access) |
| Ad Trackers & Behavioral Data | ✕ NEVER | No trackers installed | None |
🔍 Live Browser Storage Inspector
Live Client Readout
Here is the exact content currently stored in your browser's localStorage by this website:
GDPR & CCPA Compliance
Under GDPR and CCPA, users have the right to request deletion of their personal records. Because GitHub Stats Studio operates 100% on the client without a backend database, we hold no records of your requests or generated cards.
Privacy Officer Contact
Have questions about client-side privacy or data handling? Reach out directly to our team: