Privacy policy

9to5 coverage stores GitHub account, organization, repository, and coverage metadata needed to provide coverage checks.

Coverage reports are parsed into run summaries and file-level coverage. Raw upload retention will be minimized as the large-upload storage flow is introduced.

GitHub OAuth tokens and upload tokens are used only to authenticate users, synchronize repository access, receive uploads, and publish coverage feedback.

MCP access exposes stored coverage metadata—such as commit identifiers, file paths, line hit states, and coverage summaries—to an authorized client. It does not fetch or return repository source. OAuth grants follow current GitHub-visible repositories; optional API tokens can be narrowed to selected repositories and are stored as SHA-256 digests.

Billing data will be processed by our payment processor once subscriptions are enabled. The app will keep local subscription state required to enforce plan access.