Your code and your data
Your source code is never stored. Here is exactly what a scan reads, what we keep, for how long, and the rights you have over all of it.
The short version
You are handing us read access to your code. You should know precisely what happens to it. This page is the precise answer, and it matches what the privacy policy says. If a claim here ever disagrees with the privacy policy, the privacy policy is the one that governs.
The headline fact: your source code is never stored. It is fetched into a single scan job, scanned, and discarded when that job exits. There is no copy kept, no backup, and nothing is trained on it. The findings stay. The code does not.
What a scan actually touches
When you sign in with GitHub, we ask for read access. That access is read-only, and it is used for two things: to list your repositories so you can pick one, and to read the one you pick. No pushes, no pull requests, no reading repos you did not choose.
The GitHub token that grants this access is encrypted. It is used only to list your repos and read the repo you select, and it is deleted when you delete your account.
The scan itself runs in an isolated, single-use job. Your code is read there, the engine checks it, and when the job exits the code is gone. A finding will point to where a leaked secret lives, but it never prints the secret in full. A report should not become a second leak.
What we keep, and for how long
We keep only what is needed to show you a report and run your account.
Your GitHub profile, meaning your id, username, email and avatar, is kept until you delete your account.
Your scans and findings, meaning the reports, scores and generated fix prompts, are kept until you delete them. For the most serious findings, a finding also keeps a short excerpt of the surrounding code, so the fix prompt can point at the exact spot. That excerpt is capped in length, it never includes a leaked secret, and it goes when you delete the scan.
Payment records are the amount and the date only. We never see your card. Those records are retained because tax law requires it.
Support messages you send are kept, and on account deletion they are unlinked from you.
That is the whole list. Your repository is not on it, because it is never stored in the first place. The only code that lives on is the short excerpt attached to a serious finding, and that goes when the finding does.
Cookies
One signed session cookie keeps you signed in. That is it. There are no advertising cookies and no tracking cookies.
Sub-processors
A few outside services help run Sentrint, for example our payment provider handling billing as merchant of record. The current list, and what each one does, is kept up to date on the privacy policy rather than repeated here, so there is one source that never drifts.
Your rights are real routes, not promises
Under India's Digital Personal Data Protection framework, and for every customer wherever you are, you have rights over your data. These are not marketing lines. They are actual features in the product.
You can export every record we hold. You can correct it. You can erase it, which removes your account and the data tied to it. And there is a grievance channel with a named person on it.
The grievance officer is Gourab Dasgupta, reachable at [email protected]. A grievance is acknowledged within 2 to 3 business days and resolved within 30 days.
Export and erase are available to you directly in Settings. No email, no waiting, no support ticket. Export hands you every record we hold. Erase removes your account and the data tied to it, subject only to the payment records that tax law requires us to retain.
The reasoning behind all of this
The design goal is simple. The more of your data we hold, the more there is to leak, and the more you have to trust us about. So we hold as little as the product can function on, we never hold the code at all, and we make the exits one click. Strict rules built into the product beat a promise on a page.
There is an honest limitation worth stating. One developer builds Sentrint. There is no large security team behind it and no compliance badge, at least not yet. What there is instead is a short, strict set of rules, built into how the product works rather than written on a page, and a one-click way out if you ever want it. The person who wrote these rules is the same one who answers your support email.
Try it
You can read all of this before you ever sign in. When you are ready, scan a repo free, one a month, no card: start a scan.