GDPR
We comply with the EU General Data Protection Regulation, Regulation (EU) 2016/679. You can ask for access to your personal data, and for it to be corrected or deleted.
Two things matter: how we treat your data, and how our reports help you meet the rules that apply to you. This page covers both.
How we comply
We comply with the EU General Data Protection Regulation, Regulation (EU) 2016/679. You can ask for access to your personal data, and for it to be corrected or deleted.
Your repositories and your reports are stored and processed on servers in the European Union: Spain is the primary region and Germany the secondary one.
Our security practices are aligned with the standard. That is alignment with its controls, not a certification.
This website sets no cookies and runs no analytics or advertising trackers, so there is nothing to consent to.
The repositories you send are deleted when the analysis ends. Only the report is kept.
A DPA under Article 28 of the GDPR is published on this website and applies to every customer.
How we help you comply
| Rule or standard | What it asks for | What you get from scancodebase |
|---|---|---|
| OWASP Top 10 and OWASP ASVSApplication security references | The reference lists most teams and auditors use for web application risks. | Each finding mapped to its OWASP category. |
| CWECommon Weakness Enumeration | The shared catalogue of kinds of software weakness. | Each finding carries its CWE identifier. |
| PCI DSSRequirement 6 | Bespoke and custom software must be developed securely and its vulnerabilities identified. | Code findings mapped to PCI DSS, plus the known vulnerabilities in your dependencies. |
| EU Cyber Resilience Act (CRA)Regulation (EU) 2024/2847 | Products with digital elements must be developed securely, ship without known exploitable vulnerabilities and document their components. | Static analysis of your own code, known vulnerabilities in your dependencies and the list of what you depend on. |
| NIS2Directive (EU) 2022/2555 | Article 21 asks for security in the development and maintenance of systems, including vulnerability handling. | A security check on every change, with a record of what was found and when it was fixed. |
| ISO/IEC 27001Annex A, controls 8.28 and 8.29 | Secure coding principles must be applied and security tested during development. | Scan results per repository as evidence that the control operates. |
| DORARegulation (EU) 2022/2554 | Financial entities must manage ICT risk across the software they build and run. | Reproducible reports for your ICT risk file. |
| SOC 2Trust services criteria | Auditors look for evidence that vulnerabilities are found and dealt with. | Dated, reproducible reports and a history of when each finding appeared and when it was fixed. |
| NIST SSDFNIST SP 800-218 | Software producers should review and analyse their code to find vulnerabilities, and respond to them. | Static analysis on every change and a record of the vulnerabilities found and fixed. |
A scan report is evidence, not a certificate. This page is a summary and not legal advice.
FAQ
No tool does that by itself. A scan report is evidence that you look for problems and fix them. Compliance also depends on your own processes and, for some standards, on an audit.
Your repositories and reports are stored and processed on servers in the European Union. Spain is the primary region and Germany the secondary one.
Our security practices are aligned with ISO/IEC 27001. We state alignment, not certification.
Yes. We comply with the GDPR, we do not sell personal data and we do not pass what you send us to third parties.