Security and data handling
What Vetoo does with your code, how long it keeps it, and what it never does.
Vetoo uses your code only to review it. Once Vetoo posts the verdict, it deletes the code.
Zero retention
Vetoo holds your code only while a review runs. It encrypts the code in transit and processes it in an isolated sandbox for each review. When Vetoo posts the verdict, it deletes the code and keeps no copy.
Vetoo keeps only the metadata around a review, never the code. That metadata includes which request Vetoo reviewed, the result, the credits used, the findings, and the votes on them. The metadata powers the app's review and usage views, and team memory. None of it holds your source.
Where the review runs
A review sends your change, and the surrounding code it needs, to model providers outside Vetoo. None of those providers train on your code. Each review runs under an agreement that keeps your code out of every training set. On an Enterprise BYOK plan, reviews run on your own model key instead of Vetoo's model access.
Your keys stay yours
Vetoo stores every credential you connect in encrypted form, and you can revoke each credential at any time.
- Vetoo stores a GitLab token encrypted, and you can revoke it at any time. Vetoo needs a token with write access to post a review to the project.
- Vetoo stores your own model key encrypted and uses it only for your reviews.
- A connected integration has read-only access. Vetoo stores its token encrypted and uses that token only while a review or an
@vetoo-reviewconversation needs it.
If you remove the GitHub App, revoke a token, disconnect an integration, or delete a key, the matching access ends at once.
Isolation between workspaces
Each workspace's reviews run in isolation. Vetoo never pools your code, or anything a review reads, with another customer's data.