Privacy Policy
Last updated: 19 July 2026
forksplorer (“we”, “us”) is currently in a pre-launch waitlist stage. This policy describes both what we do today and what the scanner will do once repo pages go live, so you know exactly what to expect at each stage.
1. What we collect today (waitlist stage)
The only personal data we collect right now is what you choose to send us by emailing [email protected] from the “Join the waitlist” link — typically your email address and any repo names you mention. We don’t run analytics, cookies, or tracking scripts on this site (see our Cookie Notice).
2. What the fork-scanner processes
forksplorer’s core product reads public GitHub data only: repository metadata, fork lists, commits, and diffs that are already visible to anyone via the GitHub API. We do not request access to private repositories, and we do not collect data from repos you haven’t asked us to scan.
From this public data we generate: ranked lists of unmerged fork features, AI-written summaries of those diffs, and cherry-pick / patch instructions. GitHub usernames and commit authorship attached to public commits are displayed as part of that attribution — the same information already visible on GitHub itself.
3. Account data (when accounts launch)
When account creation goes live we will use Clerk for authentication (Google OAuth), and will only collect the minimum profile fields Clerk requires (name, email, avatar). Account holders will be able to export or delete their data at any time — documented in full once that feature ships.
4. Where data lives
| Purpose | Subprocessor | Location |
|---|---|---|
| Website hosting & edge delivery | Vercel Inc. | EU/US edge network |
| Fork-scanner compute, database (Hasura + Postgres), and cached scan results | Self-hosted on our own Kubernetes cluster (“Jupiter”) | Self-managed infrastructure, not a third party |
We keep this list current as new subprocessors are added — check back here rather than relying on a cached copy.
5. AI-generated content
Diff summaries are generated by large-language-model calls over public commit data. No user-submitted personal data is sent to these models beyond what’s already public on GitHub. AI-generated summaries are best-effort — verify before applying any code, as noted on our homepage.
6. Your rights
You can ask us to remove any waitlist email we hold by replying to our confirmation email or writing to [email protected]. If you’re in the UK/EEA, you have rights under UK GDPR / EU GDPR to access, correct, or erase personal data we hold about you.
7. Contact
Questions about this policy: email [email protected].