reckon review
Terms Install on GitHubInstall
โ† back to home

Privacy Policy

Last updated: July 28, 2026

the short version

Reckon Review is a GitHub App that gates pull-request merges on human comprehension. It reads your repository's source only in memory to understand a change, and never stores your source code. What it does keep is the minimum needed to run the check: the pull request's metadata, the explanations reviewers write, and the grades. When you uninstall, that data is deleted.

1. Who we are

"Reckon Review" ("we", "us") is a GitHub App that blocks a pull request from merging until a human explains, in their own words, what it changes. This policy describes what data the App processes when you install it on a repository or organization.

2. What we process - and what we store (they are different)

Reckon draws a hard line between data it reads transiently and data it persists.

Read in memory only, never stored:

  • A snapshot of your repository's source code at the pull request's head commit. Reckon downloads it, builds a throwaway map of how the changed code connects to the rest of the codebase (what references it, how load-bearing it is), generates the comprehension questions, and then discards it. This happens in process memory and typically lasts a few seconds. The source and the map are never written to our database and never persisted.

Stored durably (in a Postgres database, to run the check and keep an audit trail):

  • Installation & repository metadata - the account (organization or user) that installed the App, account type, the repositories it's active on, their default branch, and the App's configuration for them.
  • Pull request checkpoints - the PR number, the head commit SHA the check attaches to, the decomposed "sub-decisions" the grader derived from the diff, the rigor level, and the check's status.
  • Explanation attempts - the text of the explanation a reviewer writes, the reviewer's GitHub login and numeric user ID, the grade, and the grader's scoring output. This is the conversation and audit trail for a gated PR.
  • A minimal user record - the GitHub numeric ID and login of reviewers who interact with the gate, used to attribute who passed a check.

3. What we never do

  • We never store your source code or persist the codebase map built from it.
  • We never run your code. Reckon reads and grades text; it executes nothing.
  • We never touch anything outside the repositories you install it on.
  • We never sell your data or use it for advertising.
  • We do not use your private source code or your explanations to train our own models.

4. Why we process this data

We process the data above solely to provide the service: to generate a comprehension check for a pull request, grade the explanation a reviewer writes, decide whether the merge gate passes, carry a pass forward when unchanged code is re-pushed, and keep an audit trail of who explained what. The legal basis is the performance of the service you requested by installing the App (and our legitimate interest in operating and securing it).

5. Sub-processors

To run the service we share the minimum necessary data with:

  • GitHub - the App runs on GitHub's platform and reads/writes via GitHub's API (webhooks in; a status check and PR comments out), using an installation token scoped to your repositories. Your use of GitHub is governed by GitHub's own terms and privacy policy.
  • OpenAI - the diff digest, the change's structural context, and the reviewer's explanation are sent to OpenAI's API to decompose the change and grade the explanation. OpenAI processes this as an API customer and does not use API data to train its models.
  • Supabase - hosts the Postgres database that stores the durable data described in section 2.
  • Fly.io - hosts the application server that runs the App.

We do not send your repository's full source code to any of these beyond GitHub itself; only the diff, its structural context, and reviewer explanations reach the grading model.

6. Retention & deletion

We keep the durable data described in section 2 for as long as the App is installed, so the gate and its audit trail keep working. When you uninstall the App from an account, or remove a repository from the installation, Reckon purges that account's or repository's data. The in-memory source snapshot is never retained in the first place.

7. Your choices

  • Advisory-only: delete the "Reckon comprehension (managed)" ruleset to keep the check but stop it blocking merges.
  • Uninstall: remove the App entirely to stop all processing and trigger deletion of your stored data.
  • Access or deletion requests: email us (see section 9).

8. Children

Reckon Review is a developer tool and is not directed to anyone under 16. We do not knowingly collect data from children.

9. Contact

Reckon Review is in beta and open source. For privacy questions, data access, or deletion requests, email [email protected], or open an issue on the project's GitHub repository via the GitHub App page.

10. Changes

If this policy changes, we'll update the date at the top. Continued use of the App after a change means you accept the revised policy.

โ† back to home  ยท  terms of service โ†’

reckon review
FAQ Privacy Terms Contact GitHub

Reckon Review. Understand what you merge. A GitHub App. Beta.