
AudioEye and GDPR
CertReports found no public GDPR evidence for AudioEye 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
- Scope
- We use the information collected via web forms and traditional web activity, including: providing our services to users, managing customer relationships, responding to user inquiries, enforcing our terms of use, personalizing the Services and user experience on the Website, providing information regarding careers with us, and engaging in marketing activities, such as providing newsletters, publications, updates, and other information that we believe might be of interest to users. AudioEye will not use the contents of any speech data provided to us through end-user use of the AudioEye Product for any purpose except as set forth herein. With respect to marketing activities, certain information that users provide to us, such as first name, last name, company name, e-mail address, physical address, and phone number may be aggregated with other such data in one or more contact lists. We may then use these contact lists to send users information regarding our services via an automated mailing system and/or to send users surveys via an automated survey generation system. These contact lists may be integrated into our client relation management (CRM) system and/or our internal e-mail contact lists).
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | AudioEye, Inc.: Inactive | Live pagesha256 8fcaf01e05 |
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 AudioEye 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 Compliance and GRC category) whose GDPR row is verified or vendor-stated, ranked by similarity.