Effective 16 November 2026
Vitasta reads code to find calls to AI models and APIs that are being retired. This page says exactly what it reads, where that happens, what it keeps and for how long. The short version: your code is read on our server only for the length of one scan and then deleted, nothing from it is stored, and we don't sell data or train models on it.
When you install the Vitasta GitHub App on a repository, GitHub sends us events for it (installs, pushes to the default branch, pull requests, edits to Vitasta's own tracking issue). For each event we:
Where: on our own server at Amazon Web Services (AWS Lightsail) in Mumbai, India. Copies of code live only in a temporary folder on that server's disk, which is not backed up and has no snapshots.
What we keep: nothing from your code. Server logs record the event type, the repository name, the pull request number, whether a push was to the default branch, and counts (for example "3 findings"). They never contain code, snippets, file contents, tokens or branch names. Logs are kept for at most 30 days.
When you tick "Not an issue" on a finding, that choice stays in your repository's issue. We count, in memory, how often each rule and each public feed record is dismissed, with no repository, file or user attached, to learn which checks are noisy.
Stopping: uninstall the App from your GitHub settings. From then on we receive nothing for those repositories. You can delete the tracking issue and close our pull requests yourself.
These run on your own machine or CI runner and read your code there. Your code never leaves it. To know which
retirements apply, they ask our lookup service at app.vitasta.dev and send, for each distinct thing
found, only:
| Sent | Example |
|---|---|
| Provider (built-in ones only) and kind of use | openai, SDK call |
| Public model IDs (not fine-tune names or Azure deployment names) | gpt-4o-mini |
| HTTP method and API version, with the rest of the path blanked | GET /repos/acme/app/issues is sent as GET /{}/{}/{}/{} |
| Pinned API version and cloud host | 2023-06-01, Azure |
Never code, snippets, file names, line numbers, the repository name, method or parameter names, or your
.vitasta.yml. The tool matches the answer against your code on your machine. It
prints a notice each time it looks something up. With --feed <folder> it uses a local copy and
sends nothing.
The lookup service doesn't log what was asked. It keeps your IP address in memory for a few minutes to limit how often one address can ask, and logs only hourly totals.
No cookies, no analytics, no tracking. Pages load fonts from Google Fonts, so Google sees your IP address when you visit. Our web server doesn't keep access logs.
| Service | Why | Where |
|---|---|---|
| Amazon Web Services | Our server | Mumbai, India |
| GitHub | Where your code lives, and how the App receives events and posts results | GitHub's own locations |
| Let's Encrypt | HTTPS certificates (no user data) | |
| Google Fonts | Fonts on this website | Google's own locations |
We don't sell or share data with anyone else, and we don't use your code to train AI models.
You can ask what we hold about you, or ask us to delete it, at privacy@vitasta.dev. For most people the answer is nothing beyond 30 days of logs naming their repositories. To report a security problem, see Security.
If this policy changes, we'll update this page and the date above.