No public evidenceKami and GDPR
CertReports found no public GDPR evidence for Kami 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
- 16 Oct 2019
- Scope
- In order to create an account, Kami does require that all users to either create a username and password, which is stored on the site or connect via SSO with third-party SSO provider like Google or Microsoft, Kami requires Email and fisr/last name to use its functionality. Technologies such as cookies, tokens, tags and scripts are used by Kami. These technologies are used to make it easier for you to navigate our site, pass authorisation on to LMS’s, analyse trends, administer the site, tracking users’ movements throughout the site and enable fault resolution and compliance with Terms of service. As true of most Web Sites, we gather certain information automatically and store it in log files. This information may include internet protocol (IP) addresses, browser type, internet service provider (ISP), referring/exit pages, operating system, date/time stamp, and/or clickstream data. We do not link this automatically collected data to other information we collect about you. Kami collects and analyzes data on how the service is used in the aggregate for the purpose of improving and enhancing its service. Kami does not analyze information on how particular individuals use the service as part of general reporting procedures or in the usual course of business. However, information on individual usage of the system, including but not limited to individual IP addresses, may be analyzed on a case-specific basis to resolve a technical difficulty or to assist in resolving or investigating any misuse of the service. We work with a number of third-party service providers to help improve the quality of our service. These third parties do not share your information with any other third parties. Kami uses the following third-party services in the App: Microsoft – if you choose to log into Kami using your Microsoft account (often referred to as Single Sign-on or “SSO”), your login will be authenticated by Microsoft. If you open/save files on OneDrive, Microsoft will first request authorization for this. You can review Microsoft’s Privacy Policy for use of your Microsoft account here; and update or revoke your permissions as described here. Google – if you choose to log into Kami using your Google account, your login will be authenticated by Google. If you open/save files on Google Drive, Google will first request authorization for this. You can review Google’s Privacy Policy for use of your Google account here; and update or revoke your Google Permissions here. Groove – Groove is a platform our Support Team use internally to coordinate customer support activities in response to requests from our customers. Our contractual agreement with Groove complies with the terms of this policy. Google Analytics & Tag Manager – an analytics service used to help analyze your use of our Website and allow us to improve our Service and provide you information on the Service. Our agreement with Google complies with the terms of this policy. Stripe – when you upgrade your account online using a credit card, your payment is securely processed using Stripe’s e-payments service. Our contractual agreement with Stripe complies with the terms of this policy.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Kami: Inactive | Live pagesha256 04844a80c4 |
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 Kami 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.