Privacy Policy
This policy describes what information GitFun ("the protocol", "we") collects through this website and related services, how we use it, and the choices you have. GitFun is a non-custodial protocol: we never hold user funds and do not maintain accounts in the traditional sense. Most user data lives on a public blockchain that is outside our control.
1. Information we collect
1.1 On-chain data (always public)
When you interact with GitFun smart contracts, the following is recorded permanently on the Base blockchain by you, not by us:
- Your wallet address
- Tokens deployed, traded, transferred
- Liquidity positions and fees claimed
- Timestamps and gas paid
This data is public and immutable. We index it for display purposes but do not control its existence or distribution.
1.2 GitHub identifiers (when you sign in)
To verify ownership of a repository for fee claiming, you may sign in with GitHub. We receive: GitHub user ID, login, name (if public), avatar URL, and the list of repositories you maintain. We do not request access to private repositories, private email, or any write permission.
1.3 Operational telemetry
- Server logs. Standard request logs (IP, user agent, path, status code, timestamp) for the last 7 days, used for debugging and abuse prevention.
- Error reports. Uncaught exceptions are sent to Sentry, scrubbed of wallet addresses and tokens. Retained 30 days.
- Aggregate analytics. Privacy-preserving counts (page hits, unique visitors via hashed IP) only. No third-party ad networks.
1.4 What we do not collect
- Private keys, seed phrases, signing material
- KYC documents, government IDs, financial information
- Email address (unless you contact us)
- Browsing data outside GitFun domains
2. How we use information
- Operate the website and indexer
- Verify repository ownership for creator fee claims
- Detect and prevent fraud, spam, and protocol abuse
- Debug errors and improve the product
- Comply with legal obligations
We do not sell, rent, or trade personal data. We do not use it for advertising or third-party profiling.
3. Sharing
We share data only with these categories of third parties:
- Infrastructure providers (RPC: Alchemy / Infura; hosting: Vercel; error tracking: Sentry; database: Vercel KV) — bound by their respective DPAs.
- GitHub — when you authenticate, GitHub sees the login attempt under their privacy policy.
- Public blockchain — every transaction is globally readable by definition.
- Law enforcement — only on valid legal process and only the data we actually have.
4. Retention
- Server logs: 7 days
- Error reports (Sentry): 30 days
- Indexer cache: rebuilt continuously, no PII
- GitHub session token: until you sign out or token expires
- On-chain data: retained by the blockchain forever (out of our control)
5. Your rights
Depending on your jurisdiction (GDPR / CCPA / similar), you may have the right to access, correct, or request deletion of personal data we hold. Note that we cannot delete on-chain records or blanket your wallet address from the blockchain — those are not within our control.
To exercise these rights, email privacy@gitfun.xyz. We respond within 30 days.
6. Cookies
We use a single first-party session cookie to maintain your GitHub login state. We do not use tracking cookies or third-party advertising cookies.
7. Children
GitFun is not intended for users under 18. We do not knowingly collect data from minors. If you believe a minor has interacted with the protocol, contact us and we will assist appropriately.
8. International data transfers
Our infrastructure providers may process data outside your country of residence. By using GitFun, you consent to such transfers subject to appropriate safeguards.
9. Changes
We may update this policy. Material changes are announced on the homepage at least 14 days before they take effect. The effective date at the top reflects the most recent revision.
10. Contact
Questions or requests: privacy@gitfun.xyz.
This page is a draft. It has not been reviewed by counsel. Do not rely on it as legal advice. The protocol operator should engage a lawyer in their jurisdiction before public mainnet launch.