Terms of service
These terms are written from what the product does. Where a term could be vague, it names the thing that decides it: a permission, a price, or the state machine that admits a scan.
Last updated 2026-10-03These terms cover the iterative-sh GitHub App and the sites iterative.sh and app.iterative.sh. They are between iterative and the GitHub account that installs the App. Installing it, or signing in to the dashboard, accepts them.
Install it on repositories you are entitled to have read and analysed. GitHub's installation screen decides which repositories that is, and the owner of a personal account, or on an organization whoever GitHub reports as an administrator of every repository the installation covers, is who may administer the installation here.
It reads the repositories you selected and opens one GitHub issue per bug it finds, with the path, the line, the evidence and a recommended fix. It holds Contents: read and Issues: write and nothing else: it never opens a pull request, never pushes a commit, a branch or a status check, and never writes code.
What happens to your code, and what is stored afterwards, is the privacy policy's subject. Read it before installing; it is short and it is specific.
You pay per scan. For a limited time, the first scan of an installation is free; that offer may end, and ending it never charges a scan that was already admitted as the free scan. The price of a scan is published on the landing page. There are no seats, no per-user pricing and no subscription that bills whether you scan or not.
A scan is charged to your saved card before it runs, at the price of the code it will read, counted from the repository's file listing before anything is downloaded. A scan that fails, is cancelled, or does not finish inside its bound is refunded in full, automatically. A scan that reads fewer characters than it was charged for is refunded the difference. A scan that finds nothing still read the whole repository and keeps its charge.
Stripe is the payment processor. Card details go to Stripe and never to us; the dashboard's billing buttons open Stripe's own Checkout, which saves a card and charges nothing, and its customer portal.
Every scan is admitted one at a time, and admission is refused when the free scan is used up and no card is saved, when a charge has failed, or when a charge was disputed. The dashboard states which of those it is and what clears it. Nothing is charged while scanning is refused, and a charge that failed is not retried until the card is updated.
The analysis is a model reading your code. It misses bugs, and it can file an issue that is wrong. Duplicates are prevented by the finding's fingerprint and a filing lock; before that fingerprint was keyed to what two copies of a finding agree on, it filed one bug twice on our own repository.
Treat a filed issue as evidence to check, not as a verdict. You decide what changes; the App cannot change anything itself.
The service is provided as it is, with no warranty and no uptime commitment. Support is hi@iterative.sh.
We claim no rights in your code. The permission you grant is to read the repositories you selected, during a scan, and to open issues in them. Those issues are yours, in your repository, and they outlive the installation.
Do not point the App at code you are not entitled to have read. Do not use it to attack the service, the model provider, another tenant, or the GitHub accounts it can reach. An installation that does may be suspended.
Uninstall the App on GitHub. That is the off switch: the installation is marked removed and no new scan may run. Remove your card in Stripe's customer portal, which the dashboard's Billing page opens. What is kept afterwards, and how to have it deleted, is in the privacy policy.
To the extent the law allows, iterative's total liability for any claim arising out of the service is limited to what you paid for scans in the twelve months before that claim. That covers a bug the analysis missed, a change you made on the strength of a finding, and anything downstream of either.
These terms carry a last-updated date and a material change moves it. Using the App after that date accepts the change. Questions go to hi@iterative.sh.