Skip to main content
EASA logo

EASA

GDPR evidence

GDPR mark, CertReports state No public evidenceNo public evidence

EASA and GDPR

CertReports found no public GDPR evidence for EASA 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

ExpiredInactive
as of 17 Sep 2026 · confidence 100%
Kind
listing
Issued or listed
7 Jan 2019
Scope
EASA collects personal data from Customers when they purchase its products and services, and from prospective Customers when they register with our website, log-in to their account, complete surveys, request information, download information, register for events and webinars, purchase documents from our on-line store, complete web-based forms or otherwise communicate with us. EASA may also, when providing managed hosting services, collect personal data from our Customers' customers and prospective customers, since they are using our software and hosting services to develop and deploy a quoting / proposal generation system. The personal data that we collect may include some or all of the following: contact name, work or personal email address, work mailing address, work telephone number, job title, and company name. The EASA web site is PCI compliant. EASA does not retain or store any credit card information nor any personal data beyond that mentioned above.
SourceCapturedQuoteLinks
Data Privacy Framework list
Official registry · HTTP 200
17 Sep 2026EASA Inc: Inactive
Live pagesha256 c771ad0602
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 evidence

Questions buyers ask

Is EASA 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 No-code and automation category) whose GDPR row is verified or vendor-stated, ranked by similarity.

No No-code and automation vendor has GDPR evidence in the index yet.