Privacy

Random GitHub is intentionally simple. It does not require an account and does not use advertising or third-party analytics.

GitHub personal access tokens

You may optionally provide a fine-grained GitHub personal access token so Random GitHub can use your GitHub API allowance instead of the site's shared allowance.

Your token is stored only in the server-side session. The browser receives a session cookie containing a session identifier, not the token itself. The token is sent only to GitHub's API and is removed when you choose Forget token, when the session expires, or when GitHub rejects the token.

Random GitHub does not include your personal access token in logs or Mission Control telemetry.

Mission Control telemetry

When a random repository is successfully selected, Random GitHub may send an event to my private Mission Control service for basic operational and usage telemetry.

The event may include:

• The selected repository ID and name
• Language, star count, and fork count
• Whether the repository is a fork
• Repository creation and last-push dates
• Whether the Skip forks option was enabled
• Whether a personal GitHub token was being used
• Whether the repository had a README
• How long the random selection took

The Mission Control event does not include your GitHub token or your GitHub account identity.

Cookies

Random GitHub uses a session cookie when needed for features such as the optional personal GitHub token. It is not used for advertising or cross-site tracking.

External services

Random GitHub communicates with GitHub's API to retrieve public repository information and rendered README content. Repository READMEs may also contain images hosted by GitHub or other external sites, which your browser may request when displaying the README.

Hosting, reverse-proxy, and network infrastructure may also process normal request information such as IP addresses as part of serving the site.