Legal
Privacy Policy
Last updated: May 22, 2026
This policy explains how Good First Issue handles account information, GitHub-connected workflows, indexed public GitHub data, analytics, logs, and cookies.
Overview
Good First Issue helps users discover beginner-friendly open source issues and repositories. This policy explains the information we process to operate that service.
This policy is informational and should be reviewed by qualified counsel before relying on it as legal advice or as a final legal policy for production use.
Account information
When you sign in, authentication is handled by Clerk. The app may receive and display profile fields exposed by Clerk, including your Clerk user ID, first name, last name, full name, username, profile image URL, primary email address, primary phone number, account creation date, and update date.
We use this information to authenticate requests, show account state, support user-specific GitHub workflows, and troubleshoot service behavior.
GitHub OAuth usage
If you connect GitHub through Clerk, the service may request GitHub OAuth access tokens from Clerk for repository import, issue fetching, and issue status synchronization tasks.
We use those tokens to call GitHub APIs for the workflows you initiate or authorize. We do not intentionally display GitHub OAuth tokens in the product UI, and server logging is configured to redact common token, access token, refresh token, and authorization fields.
Public GitHub data
The service stores indexed public GitHub data needed for discovery and synchronization. This may include repository identifiers, names, owner names, URLs, stars, forks, language, issue counts, last commit timestamps, processing timestamps, descriptions, issue identifiers, issue titles, issue URLs, issue body text, issue numbers, creation dates, issue states, assignee counts, comment counts, reaction counts, labels, and related pull request references.
This data originates from GitHub and public repositories. It may be stale, incomplete, or removed from GitHub after it has been indexed here.
Analytics
We use Google Analytics to understand aggregate site usage, such as page visits and interaction patterns. Analytics providers may collect identifiers, device information, browser information, approximate location, referral information, and usage events according to their own policies and configuration.
We use analytics to improve navigation, content, reliability, and product decisions.
Operational logs
The service uses pino-based server logging for operational visibility, debugging, abuse prevention, and reliability work. Logs may include route names, request status, user IDs, repository identifiers, repository URLs, error details, and task progress metadata.
Logging is configured to redact common authorization and token fields, but you should not put secrets into repository descriptions, issue content, names, URLs, or other public fields that may be indexed from GitHub.
Cookies and sessions
Clerk and analytics providers may use cookies, local storage, or similar technologies for sign-in sessions, security, fraud prevention, preferences, analytics, and service measurement.
Your browser may let you block or delete cookies, but doing so can prevent authentication or analytics-dependent behavior from working as intended.
Sharing
We share information with service providers only as needed to operate, secure, host, measure, and maintain the service. These providers include authentication, GitHub API, analytics, hosting, database, logging, and infrastructure providers.
We may also disclose information if required by law, to protect the service, to investigate abuse or security issues, or as part of a project transfer or reorganization.
Retention
We keep information for as long as needed to operate the service, maintain indexed public GitHub data, troubleshoot issues, comply with legal obligations, and protect the service.
Because much of the indexed content comes from public GitHub repositories, deleting or changing content on GitHub may not immediately remove previously indexed copies from this service.
Your choices
To request access, correction, deletion, or other privacy help, contact the project through the Good First Issue GitHub organization. We may need enough information to verify the request and identify the relevant account or indexed data.
Contact: https://github.com/goodfirstissueorg