Privacy policy

Public GitHub data. When you scout a profile or browse country squads, we fetch public GitHub information (for example: username, avatar, repositories, contributions, and location when listed on GitHub). We turn that into player cards and rankings. We do not access private repositories.

Account data. If you sign in with GitHub, we store your GitHub user id, login, name, email (if shared by GitHub), and profile image so we can run your session and dashboard.

Claimed profile details. Developers who claim a profile may add availability, a contact email, a contact URL, rates, and a short bio. You choose what to publish.

Requests and messages. Clients may post hiring requests and send messages to developers. We store request text, message bodies, timestamps, and the accounts involved so threads can be shown in the dashboard.

Usage and technical data. We may log IP-derived country (for default squad selection), page views, scout counts, search queries, and basic error logs. Your browser may store squad and card cache locally (IndexedDB and localStorage) to speed up repeat visits.

We use collected data to:

• Score and display developer cards from GitHub output
• Run national lineups, search, and client shortlists
• Authenticate users and operate the claim and messaging features
• Send email notifications related to requests and replies (when enabled)
• Improve reliability, prevent abuse, and understand aggregate usage

We do not sell your personal data.

Gitwork relies on external providers, including:

• GitHub for OAuth sign-in and public profile data
• Vercel for hosting and analytics
• Neon for application database storage
• Upstash Redis for caching and rate limiting
• Resend for outbound and inbound email (when configured)

Each provider processes data under its own terms. We only share what is needed to run the service.

Sign-in uses session cookies managed by our auth system. We also use browser storage for theme preference, your selected country squad, and cached scout results. You can clear site data in your browser settings at any time.

Account, claim, request, and message records are kept while your account or the relevant content exists, unless we must delete them sooner for legal or operational reasons. Cached GitHub card data may be refreshed or expired over time. Aggregate analytics may be kept longer in anonymized form.

• Browse without signing in (limited features only)
• Update or remove claim details from your dashboard
• Clear local browser cache for this site
• Contact us to ask about access, correction, or deletion where applicable

Because much of Gitwork is built from public GitHub profiles, removing data from Gitwork does not remove information already published on GitHub.

Questions about this policy or your data: hello@getuigen.dev