Privacy Policy
Last updated September 27, 2026
What this covers
ChangeVerify checks one AI code change at a time. This policy describes what happens to the original task and Git diff you paste, and to the verification report produced from them.
What you submit
You choose what to paste. That usually includes the original instruction you gave an AI coding tool and the Git diff for that change. Do not include secrets such as API keys, passwords, access tokens, or private keys.
ChangeVerify does not access your repository. It only analyzes the text you submit.
How the submission is used
The original task and Git diff are sent to ChangeVerify and then to a third-party AI model provider to produce this verification report. They are used for that verification, not to build a code history.
ChangeVerify does not keep a database of your code. Server logs record request details such as character counts and token counts. They do not record the task text or the diff text.
The report can be kept in an encrypted token in your browser session for a short time so you can unlock that same report. The token holds the report, not the raw task or diff. Closing the tab or starting another check removes that session data.
Payment
Checkout is handled by Creem. ChangeVerify does not receive or store your card number. The purchase is a one-time payment for the current verification report.
Accounts
ChangeVerify does not create a user account for this check.