What GGGGGIT! actually collects, why, and how to have it removed. Plain, short, no filler.
Two separate things, neither shared with the other:
If you sign in with GitHub (to heart entries): your GitHub id, username, avatar, and whatever heart button you click. Which repos you've hearted is private — visible only to you. The total heart count per repo is public.
If you submit a repo (footer form): the repo URL and whatever note you added. No account or email required to submit.
Want new entries as they're added? That goes through Buy Me a Coffee now, not this site — whatever you share with them for that is covered by their own privacy policy, not this one.
The GitHub sign-in exists so hearting can actually persist per person. Submissions exist so anyone can flag a repo worth including — Alexander reviews each one by hand before anything's added to the library.
Both are stored in a Postgres database with row-level security enforced by the database itself, not just application code. Your individual heart list is never exposed through GGGGGIT!'s public API — the only public number is the aggregate heart count per repo, which never reveals who hearted what. Submissions aren't readable back out through the public API either — only Alexander sees them, via Supabase Studio.
Email hello@paschkastudio.com with the GitHub account or submission in question and it comes out. No form, no waiting on a vendor — this is a small, self-run database, not a platform.
Data lives in Supabase (the database/auth provider) and, if you sign in with GitHub, GitHub's own OAuth flow (governed by GitHub's privacy statement). Nothing here is sold, and none of it is used for advertising.