
OPSWAT and GDPR
CertReports found no public GDPR evidence for OPSWAT as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Issued or listed
- 25 May 2018
- Scope
- We collect personal data that we believe to be relevant and required to provide an individual visitor or customer (and, by extension, the organization they represent) with access to requested information and services and to conduct our business. Personal data collected includes: First Name. Last Name. Company Name. Email Address. Phone Number. Industry of Company. We collect and process personal data for the purposes set forth below: Verify identity of visitors and customers entering our physical office locations. Verify identity and entitlement of visitors and customers to our products and services Additionally, we process personal information collected to: Respond to inquires. Permit registration by visitors and customers (and by extension the organizations they represent) to participate in the following activities: Application for open work positions Participate in user surveys Activate product licenses Access white papers
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | OPSWAT, Inc.: Inactive | Live pagesha256 8a553e3b58 |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is OPSWAT GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags or the Security category) whose GDPR row is verified or vendor-stated, ranked by similarity.