Where does personal data go in your code?
Paste a public GitHub repository. We trace the personal data it handles to every log, database and third party it reaches, with the file and line for each step. Free, no sign-up.
01 · ScanPUBLIC REPOSITORIES
Scan a public repository.
Scan a public repository. We do not store your code: we process it to generate the findings, then discard it. We will give you this in writing.
Want to run it locally in your IDE? Check out our integrations.
THE DATA MAP
Every personal-data field the code handles, and the path it takes from where it comes in to where it lands.
THE THIRD PARTIES
Which outside services receive personal data, named from the code: payment, messaging, analytics, AI.
THE FINDINGS
Personal data in logs, stored without protection, or sent without encryption, each cited to the law it falls under.
Questions
- What does the scan look at?
- The source code of a public GitHub repository. It finds the personal data the code handles, from names and phone numbers to identity numbers and health data, and traces where each one goes: into logs, into databases, and to third-party services.
- Do you keep my code?
- No. The repository is downloaded to run the scan and discarded afterwards. What is kept is the result: the findings and the data map.
- What about private repositories?
- Sign up and connect GitHub, or run the scanner in your own CI or editor, so the code never leaves your environment.
- How long does it take?
- A few minutes for most repositories. Very large ones take longer, and the result page shows progress while it runs.