KenMeet is built to support teams that need to meet, record, and collaborate responsibly. This Compliance Center summarizes the data protection principles, security practices, and legal frameworks that shape how we operate the Service. It works alongside our Terms & Conditions, Privacy Policy, and Cookie Policy, which remain the governing documents for your use of the Service.
01 Our Approach to Compliance
We design KenMeet's infrastructure, product features, and internal processes with data protection and operational resilience as first-order concerns — not an afterthought. This means limiting how meeting content is used, being transparent about AI processing, and building our multi-region architecture with redundancy and security controls in mind.
This page is intended as a plain-language summary for customers, security reviewers, and procurement teams. It is not a substitute for the full terms of our legal agreements.
02 Data Protection Regulations
Depending on where you and your organization are located, your use of KenMeet may be subject to regulations such as the General Data Protection Regulation (GDPR) in the EEA/UK, the California Consumer Privacy Act (CCPA), and other regional data protection laws. Our Privacy Policy describes the rights available to you under these frameworks, including access, rectification, erasure, and restriction of processing.
Where we act as a data processor on behalf of an organization's KenMeet account (see our Privacy Policy's "Role of the Meeting Host" section), that organization is generally the data controller responsible for its own compliance obligations toward its users.
03 Security Measures
- Encryption: data is encrypted in transit and, where appropriate, at rest.
- Access Controls: internal access to systems and data is limited and controlled based on role and necessity.
- Regular Assessments: we conduct periodic security reviews of our systems and infrastructure.
- Resilient Architecture: our multi-region SFU (Selective Forwarding Unit) deployment is designed to maintain call quality and availability even under regional disruptions.
No system can guarantee absolute security, and these measures are described in more detail in our Privacy Policy and Terms & Conditions.
04 Sub-processors and Vendors
We rely on a limited set of third-party providers to help operate the Service, including:
- Payment processing — Stripe, for handling subscription billing. We do not store full payment card details on our servers.
- Infrastructure and hosting — across multiple regions to support performance and redundancy.
- AI processing partners — used solely to power transcription and notetaker features for the specific meeting they relate to, under confidentiality and data processing terms.
- Analytics providers — used to understand aggregate, typically anonymized, usage patterns.
All sub-processors are contractually bound to use data only for the purposes for which they are engaged and to apply appropriate safeguards.
05 AI Processing and Confidentiality
Where third-party AI providers are used to support these features, they operate under strict confidentiality and data processing terms. Because AI output may not always be fully accurate, we recommend reviewing and verifying transcriptions and notes before relying on them for important records or decisions.
06 Data Residency and Transfers
Our multi-region infrastructure means information may be stored and processed in different countries. For customers in the EEA or UK, where data is transferred outside those regions to countries without an adequate level of data protection, we apply appropriate safeguards such as Standard Contractual Clauses. Further detail is available in our Privacy Policy.
07 Your Rights and Requests
You may have rights to access, correct, delete, or restrict the processing of your personal information, depending on your jurisdiction. Requests can be submitted using the contact details below, and we will respond in accordance with applicable law. If your account is managed by an organization's administrator (a Host), some requests may need to be directed to that organization first.
08 Children's Privacy
The KenMeet Service is not directed at, or intended for use by, individuals under the age of 13, and we do not knowingly collect personal information from children under this age. If we become aware that we have done so inadvertently, we take steps to delete that information promptly.
09 Incident Response
We monitor our systems for security issues and maintain internal processes for identifying, containing, and addressing incidents that may affect the confidentiality, integrity, or availability of the Service. Where an incident affects your personal information, we will take appropriate steps to notify affected parties and relevant authorities as required by applicable law.
10 Policy Documents
For the full legal detail behind this summary, please refer to:
11 Contact Our Compliance Team
For compliance questions, security reviews, data protection inquiries, or to exercise your data rights, please reach out to:
Questions about compliance or security?
info@kenzgroup.org
Video Call Demo
Team Meeting
Screen Sharing
Whiteboard & Tools
Video Meetings
Screen Sharing
Team Messaging
AI Assistant
Copilot for Gmeet (Coming Soon!)
Copilot for Zoom (Coming Soon!)
Copilot for Teams (Coming Soon!)