What GitObs reads, and what it keeps

You connect GitObs through GitHub. Signing in asks for your email address, read access to your organizations and access to the repositories you choose to analyze. GitHub lists exactly what was granted on its authorized applications page.

To count line changes per file, a worker clones each connected repository into temporary storage and walks its commit history. The clone is deleted when the repository is next processed and is cleaned up after two hours at the latest.

For each commit, GitObs stores:

• The commit hash, parent hashes and date
• The author’s name and email address as recorded in Git
• The commit title and message
• The paths of the files that changed, with lines added and removed per file

File contents are not stored. GitObs also keeps pull request, release and contributor details from the GitHub API, plus your account and organization settings.

Revoke GitObs in your GitHub settings at any time; syncing stops immediately. To have your data deleted, email hello@gitobs.com from the address on your account.

If you find a security issue, email hello@gitobs.com with the details and how to reproduce it.