GitHunt is operated by Aadin Kc, based in Kerala, India. For any privacy question, complaint, or data request, contact hey.itsaadin@gmail.com.

Account information

When you sign up, we store your username, a securely hashed password (we never store your actual password), and optionally your email address. If you sign in with Google or connect a GitHub account, we store the name, email, and profile photo Google/GitHub shares with us, and your GitHub username/ID if you connect it. If you add a GitHub personal access token to raise your GitHub API rate limits, we store that token encrypted, and only decrypt it server-side when making a request to GitHub's API on your behalf.

Profile information

Display name, bio, avatar image, and cover/background image, if you choose to add them.

Content you post

Posts, replies/comments, images you attach, links you share, and any GitHub repository data you attach to a post. Posts and comments are public to anyone using the app unless you delete them.

Usage data

A signed session cookie that keeps you logged in, and a short-lived cookie used only during Google sign-in to prevent forged login requests. We do not use advertising or third-party tracking cookies.

Engagement with repos (signed-in users)

If you're signed in, we keep a record of how you interact with repo cards in the feed — expanding a README, opening Ask AI, clipping/unclipping a repo, sharing, clicking through to GitHub, marking a repo "not interested," and roughly how long a card was visible on your screen before you scrolled past it. Each of these is tied to your account and stored server-side (not just in your browser). We use this only to shape which kinds of repos your own feed shows more or less of — for example, favoring the languages and topics you engage with and showing less of what you consistently scroll past or mark as not interested. Marking a repo "not interested" also adds it to a short, separate list of repos we stop showing you specifically — that list clears itself automatically after three weeks, or sooner if you don't use GitHunt for a full week. We keep a rolling window of your recent activity and a bounded summary of your interests rather than an ever-growing history — older detail is regularly cleared out once it's no longer needed to keep your feed relevant. This data is not shared publicly, not sold, and not used for advertising. You're in direct control of it: Settings > Personalization lets you turn this off entirely (which deletes the data and stops any more being collected) or clear it and start fresh without turning it off, with no need to contact us.

Locally on your device

Your browser stores which posts/comments you've liked or reposted, so the heart/repost icons stay filled in on your device. This never leaves your browser and isn't tied to your account. (This is separate from repo engagement tracking above, which is account-tied and server-side.)

• To create and secure your account, and keep you signed in.
• To display your posts, replies, and profile to other users.
• To send account emails, such as verifying your email address.
• To fetch public repository data from GitHub when you attach a repo to a post.
• To personalize your own feed based on how you've engaged with repos (see "Engagement with repos" above) — this only affects what's shown to you, not to other users.
• To respond to reports and enforce our Terms of Service.

We do not sell your personal information, and we do not run ads on this app.

We use a small number of third-party services to run the app. We don't sell data to anyone.

• Neon — hosts our Postgres database, where account and post data is stored.
• Vercel — hosts the app itself.
• Resend — sends account emails (like email verification) on our behalf.
• Google and GitHub — used only if you choose to sign in with Google or connect a GitHub account, to verify your identity or fetch public repo data.
• Groq — powers GitHunt AI (see below). Whatever text you send it is processed by Groq to generate a response.
• Google Translate and MyMemory — power in-app translation of repo cards. When you translate a card, its description, topics, and README text are sent to one of these services to be translated; we fall back from Google to MyMemory if the first is unavailable. Neither is used unless you use the translate feature.

GitHunt AI is an assistant feature built into two places in the app, powered by a third-party model provider (Groq, currently running an open-weight model). Neither feature stores or reuses your questions to train any model — GitHunt has no control over, and doesn't rely on, how Groq itself may log requests on its end for abuse prevention.

Where it's integrated

• Feed search bar — the search box at the top of the feed sends whatever you type to GitHunt AI first, which turns it into repository search keywords and an optional language filter. That interpreted query (not a copy of the repo results) is then run through GitHub's own search API, the same as any other search in the app.
• "Ask AI" on repo cards — expanding "Ask AI" on a repo card opens a chat scoped to that one repository. Your question, the recent turns of that conversation, and public details about the repo (name, description, language, topics, star/fork counts, its GitHub URL, and a short README excerpt) are sent to the model so it can answer in context.

What we log

We keep a lightweight usage record of each AI request — your account ID (if signed in), IP address, which repo a chat was about (if any), the model used, token counts, response time, and whether it succeeded. This is for abuse prevention, rate-limiting, and monitoring the feature's health, not for building a profile of what you've asked. We do not log the content of your questions or the AI's replies in this record.

Rate limits

Both AI features are rate-limited per IP address and, if you're signed in, per account, to keep the feature available and prevent abuse.

Permissions and scope

GitHunt AI only ever reads: what you type into it, the recent turns of the current chat, and public repository metadata already visible on the card. It cannot access your account, private messages, other users' data, or any GitHub data beyond what's shown on the card — and it cannot take actions on your behalf (it doesn't post, follow, star, or modify anything).

We keep your account and content for as long as your account exists. You can delete individual posts and replies at any time from within the app. You can also delete your account entirely, yourself, at any time from Settings → Manage account (you'll be asked to type your username to confirm). This removes your account and associated personal data immediately; posts and replies you made are kept so replies and threads stay intact for other users, but are no longer attributed to you. If you'd rather we handle it for you, or you run into any trouble, you can also contact hey.itsaadin@gmail.com and we'll remove it manually.

Under India's Digital Personal Data Protection Act, 2023 and other applicable law, you can ask us to access, correct, or delete your personal data, or withdraw consent you previously gave. To exercise any of these rights, contact us using the details above.

This app isn't directed at children, and we don't knowingly collect personal data from anyone under 18. If you believe a child has created an account, contact us and we'll remove it.

In accordance with the Information Technology Act, 2000 and the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, the Grievance Officer for this app is:

Jacob
jacobjohns823@gmail.com
Will be updated soon

We may update this Privacy Policy from time to time. If we make material changes, we'll update the "Last updated" date above.

This policy is governed by the laws of India.