No public evidenceInsidewave and GDPR
CertReports found no public GDPR evidence for Insidewave 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
- 1. Personal data we handle for our customers (“Service Data”). We collect this data through our Karmaddress platform, additional Karmaddress products, and related training, support, consulting and professional services. We refer to all of these offerings as the “Services.” Under applicable law, Karmaddress is considered a “processor” of this data, and our customer is the “controller” of the data 2. Personal data we handle for our own business (“Business Data”), other than for our own human resources activities. This includes certain data collected on our own website, such as newsletter signup forms, account signup forms, demo request forms, as well as data collected through other marketing-related efforts. Under applicable law, Karmaddress is a “controller” of this data. 1. Privacy Practices Specific to Service Data a. Types of Service Data We receive and process certain types of information from or on behalf of our customers when they use the Services. This information may include: Email Address of an individual with whom our customer has an existing business relationship; First Name, Last Name, Company Name, and Job Title of an individual with whom our customer has an existing business relationship; Other Information about an individual with whom our customer has an existing business relationship: o Current and previous companies at which an individual has worked; o Current and previous schools at which an individual has studied; o Professional Skills of an individual; o Position Descriptions from current and previous companies as listed by an individual; o Recommendations and Endorsements provided for an individual o Interests of an individual; Details about a user’s interaction with an ad, email, web site, or other communication that contains our technology; Cookie identifiers; Data described in the Cookies and Automated Data Collection section below; and Any other data that our clients choose to transmit to us (or have us collect on their behalf) to provide the Services. b. Uses of Service Data Subject to our contractual obligations, and depending on the particular Services, we use the information described above as follows: To provide the Services, including to: o allow a customer to contact an individual with whom he already has an existing business relationship; o allow a user to contact an individual with whom he already has an existing business relationship; o allow a customer to see how an individual with whom he already has an existing business relationship could introduce him to an individual with whom he does not already have an existing business relationship; o provide data and feedback to our customers in connection with the provision of our Services; o facilitate and improve the Services, which may include analyzing usage trends, tracking the types of questions we receive and providing support to our clients and visitors to our websites; To enforce the legal terms that govern the Services; To comply with law and protect rights, safety and property; and For other purposes requested or permitted by our customers or users.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Insidewave: Inactive | Live pagesha256 ecfb1c67de |
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 Insidewave 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) whose GDPR row is verified or vendor-stated, ranked by similarity.
No same-category vendor has GDPR evidence in the index yet.