Trust
Security and data handling
FiScope is a screening layer, not a certification or audit. Scores are directional. We keep the minimum we need to run an assessment for you, and account deletion removes your identity and assessment data.
What we read from GitHub
The evidence adapter collects repository metadata: default-branch protection, required reviews, required reviewers / CODEOWNERS enforcement, CODEOWNERS presence, Actions workflow names, Dependabot config, releases/tags, and glossary-doc path presence. We do not store raw private file contents — only those structured signals.
GitHub App permissions
The FiScope GitHub App requests read-only access: repository metadata, contents (to see whether protection/CODEOWNERS/docs exist), and administration/ruleset reads needed for branch-protection facts. We do not request write, org-admin, or webhook delivery of your source. Connecting an install requires GitHub sign-in so we can confirm the installation is one you can see.
GitHub sign-in
GitHub sign-in is optional (magic link remains available). It requests only read:user and user:email, and is used to confirm which FiScope GitHub App installations you can see. It never reads your repositories: private repos are read through the GitHub App install, which is the least-privilege path.
What we store
Installation IDs (not installation tokens) on your account, session cookies, assessment payloads you persist after sign-in, and anonymized usage events. Your GitHub sign-in token is encrypted at rest. Installation and user tokens are used server-side only and are not sent to the browser, logs, or metering payloads. If you signed in with GitHub before this change, you can revoke the old FiScope authorization at github.com/settings/applications.