Privacy Policy
Last updated: 1 July 2026
This Privacy Policy explains how Claudeers ("Claudeers", "we", "us") collects, uses, and shares information when you use claudeers.com and related services (the "Service").
Claudeers is an independent community and ecosystem directory. It is not affiliated with, endorsed by, sponsored by, or operated by Anthropic PBC or Claude. See our Disclaimer.
1. Who this applies to
This policy applies to everyone who uses the Service: anonymous visitors, registered account holders, listing owners who claim a project, and paying customers.
The Service is not directed to children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect data from children. If you believe a child has given us data, contact us and we will delete it.
2. What we collect
We collect only what the Service needs to function.
Account data (when you sign in with GitHub)
We use GitHub OAuth. With your authorization, GitHub provides and we store your email address, your GitHub user ID and username, your display name, and your avatar URL. We request only the minimum GitHub scopes (read:user, user:email) and never receive your GitHub password.
You may later add optional profile fields yourself: bio, website URL, social links, and — only if you request payouts — a USDT (ERC-20) wallet address. We also store your email-notification preferences and basic activity timestamps (member-since, last-active, login streak).
Content you submit
Reviews, star ratings, guestbook/wall comments, forum posts, upvotes, saved-listing bookmarks and notes, and edits to listings you own. This content (except private bookmarks) is published on the Service and tied to your profile.
Payment data
Payments are processed by Stripe. We do not receive or store your card number. We store only the Stripe identifiers (customer, session, payment, and subscription IDs), the product purchased, the amount, currency, and status. Stripe processes your payment details under Stripe's Privacy Policy.
Analytics and logs
For each page view we store a daily-salted, one-way hash of your IP address (never the raw IP), the referring URL, and your country (derived from a network header). The daily salt means the hash cannot be used to track you across days. We also keep operational logs (for example, emails sent and administrative actions) for security and debugging.
If site-wide analytics are enabled, we use Google Analytics 4, which sets its own cookies and processes data under Google's Privacy Policy. If it is disabled, no data is shared with Google.
Cookies and local storage
- Session cookie (HttpOnly) — keeps you signed in.
refcookie (30 days) — remembers who referred you, for referral credit.theme(browser local storage) — remembers your light/dark preference.- Google Analytics cookies — only if analytics are enabled.
These cookies are strictly functional or first-party analytics. See "Your choices" for how to control them.
Directory content from GitHub
Our automated scanner collects public repository metadata and README content from GitHub's public API (stars, language, topics, description, README) to build directory listings. It never accesses private repositories, and README content is sanitized before it is rendered. This is project information, not visitor personal data — but if a public README happens to mention a person, that text may appear in a listing. See our Terms of Service for the correction and removal process.
3. How and why we use it
We use the information above to operate the Service (authenticate you, show your profile, run the directory), process payments and deliver paid features via Stripe, communicate with you (transactional emails such as receipts and verification, plus digests and announcements if you opt in), measure and secure the Service (privacy-preserving analytics, abuse and fraud prevention, and rate-limiting — we hash IPs precisely so we can do this without retaining raw IPs), and operate referrals and rewards if you participate.
We rely on your consent (for example, signing in or opting into email), the performance of our agreement with you (delivering paid features), and our legitimate interests in running and securing the Service.
We do not sell your personal information.
4. Who we share it with
We share data only with service providers that help us run the Service, each handling data under their own terms:
| Provider | Purpose | Data involved |
|---|---|---|
| GitHub | Sign-in (OAuth) and public directory data | Your GitHub profile (on sign-in) |
| Stripe | Payment processing | Payment/transaction data |
| Cloudflare | Content delivery, security, and country lookup | HTTP traffic; IP to country |
| Google Analytics (if enabled) | Aggregate usage analytics | Cookie and usage data |
| Email/SMTP relay | Transactional and opt-in email | Recipient address and message |
We may also disclose data to comply with law, enforce our Terms, or protect the rights and safety of users and the public. If Claudeers is involved in a merger or acquisition, data may transfer as part of that transaction.
The Service is operated from, and data may be processed in, the United States and other countries. By using the Service you consent to this transfer.
5. Retention
We keep account and content data for as long as your account is active and as needed to provide the Service, comply with law, resolve disputes, and enforce our agreements. Hashed-IP analytics records and operational logs are retained for a limited operational period and then aged out. Deleting your account removes or anonymizes your personal data, except where we must retain records (for example, payment or tax records held by Stripe or required by law).
6. Your choices
- Email: opt out of digests and announcements in your settings or via the unsubscribe link. Transactional emails (receipts, security) cannot be opted out of while you have an account.
- Account deletion: email [email protected] to request deletion of your account and associated personal data.
- Cookies: control or clear cookies in your browser; clear local storage to reset your theme preference. Blocking the session cookie will sign you out.
- GitHub: you can revoke Claudeers' GitHub authorization at any time in your GitHub settings.
7. Security
We use reasonable technical and organizational measures, including HTTPS everywhere, HttpOnly session cookies, hashed IPs, signed payment webhooks, and server-side authorization checks. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
8. Changes
We may update this policy. Material changes will be reflected by the "Last updated" date above and, where appropriate, a notice on the Service. Continued use after changes means you accept the updated policy.
9. Contact
Questions or requests: [email protected].