Secure Access
GitHub login is required before we analyze repositories.
We use GitHub login to create your account, tie analyses to you, and load your public repositories. This build requests `read:user` and `user:email`. Private repositories are connected separately through a read-only GitHub App install after login.
What We Store
Encrypted token at rest
Your GitHub access token is encrypted in the database and never rendered back into the UI.
Private repo access is separate
If you want private repositories, you can connect them later through a GitHub App install that is limited to read-only repository access.
Analysis history belongs to you
Every analysis is linked to your account so you can revisit prior runs without exposing them to other users.
Read-focused use
Your login token is kept for identity and read-only account lookups. Private repository analysis uses a separate GitHub App connection instead of a broad `repo` OAuth scope.