Ship AI features
without losing sleep

Why this matters

Standard AI requires your expertise to identify critical vulnerabilities. We at Sentrint help you to bridge the gap and ship secure product.

Three passes over your code, only the first one decides

What happens to your code

• Built to DPDP Act 2023

  India's data-protection law, and the one we answer to. Consent you can withdraw, a breach clock, and a named officer on the hook.

  How we meet it
• Aligned with GDPR data rights

  Your access, correction and deletion rights, honoured wherever you live. We claim no certificate and no EU representative, only the substance.

  What aligned means
• Payments PCI DSS via Dodo

  Card entry is handled entirely by our payment processor, Dodo. Those details never reach, and are never stored on, a Sentrint server.

  Where money goes

• Read-only, on the repo you pick No write accessOne repo GitHub App scope How

  The GitHub App we install can read the repository you choose and nothing else. It cannot push a commit, open a pull request, change a setting or add a collaborator, because those permissions were never requested and GitHub will not grant what was not asked for.

  It also cannot see your other repositories. You pick one at install time and that choice is the boundary. Adding a second one is a decision you make in GitHub, not something we can do from our side.

  Signing in for the first time on a public repository asks only for your email address. Private-repo access is a separate step you take later, if you want it.

• Scanned in a sealed job Single-use jobGoogle Cloud Cloud Run How

  Every scan runs in its own container on Google Cloud, created for that one job and destroyed when it exits. Nothing is shared between scans, so your code never sits on a machine that is also holding somebody else's.

  The container has no route back into our application and no standing credentials. It reads the repository, produces findings, and stops existing.

  This is also why a first scan takes longer than a second one. The wait you see is a machine being built for you, not a queue.

• Your code goes when the job does No backups30-day excerpt Purge job How

  The clone is deleted with the container. There is no copy on a second disk, no backup of it, and nothing from your repository is used to train any model, ours or a third party's.

  One qualification, and it is the reason this card does not simply say zero. On CRITICAL and HIGH findings we keep about ten lines of code around the flagged line, so that a fix prompt can be rebuilt after the container is gone. That excerpt is purged automatically after 30 days.

  That excerpt is the only fragment of your source we hold at all. Everything else we keep is a finding: a file, a line number and a description.

• A key is never printed in full Never printedLive-key check Scanner How

  When the scanner finds a leaked credential, the report tells you the file, the line and what kind of key it is. It does not print the key.

  This is not politeness. A security report gets forwarded, pasted into a ticket and left open in a tab, and a report that reproduces the secret in full is simply a second copy of the leak in a place nobody is guarding.

  The one thing we do with the key is ask the provider that issued it whether it still works, because a live key and a revoked one need very different responses from you. We do not store the value.

• Export or erase it yourself One clickNo email Settings How

  Everything we hold about you downloads as a file from Settings, and the same screen deletes your account outright. Both are buttons. Neither is an email you send and then wait on.

  The export names every service that has received any part of your data, so you can check our list against your own without taking our word for it.

  Deletion removes the account, the scans and the findings. It is not a flag that hides you from the interface.

• A named person answers you 2-3 business daysNamed officer DPDP Act How

  India's DPDP Act requires a Data Fiduciary to name a Grievance Officer who answers complaints. Ours is Gourab Dasgupta, reachable at a real address printed on the privacy page. Not a form, and not support@.

  You get a reply within 2-3 business days, and the matter itself is settled inside 30 days. Business days, not clock hours: a small company cannot honestly promise a timer that keeps running over a weekend.

  These rights are not restricted to people in India. Access, correction, erasure and complaint work identically wherever you are, because running a second-class version of privacy for people whose country does not force our hand is not a trade we are interested in making.