Kenmeet was founded on a simple observation: the teams with the strictest data rules were being served worst by the meeting tools they were forced to use. We set out to fix that — starting with the regions where it mattered most.
Most video platforms were built in one jurisdiction and expanded everywhere else by exception — routing calls through infrastructure that was never designed with GDPR, Saudi PDPL, or the UAE's federal data protection law in mind. For legal, healthcare, financial, and government teams across Europe and the Middle East, that's not a minor inconvenience. It's a blocker.
We kept hearing the same thing from CISOs and compliance leads: "We love the product, but we can't confirm where the data actually lives." So we built Kenmeet the other way around — data residency and encryption came first, and the meeting experience was designed around those constraints, not in spite of them.
That means in-region processing for EU customers, dedicated infrastructure for Gulf-based organizations navigating data localization requirements, and a security architecture that's auditable by design — not by exception.
Europe's GDPR and the Gulf's newer, sovereignty-driven data laws differ in real ways. Rather than force a single compliance posture on both, we designed Kenmeet's infrastructure to meet each region on its own terms.
GDPR set the global bar for consent, data-subject rights, and cross-border transfer accountability — with fines that have run into the billions for platforms that got it wrong.
Saudi Arabia's PDPL and the UAE's federal data protection law are newer than GDPR, but often stricter on data localization — treating where data sits as a matter of national digital sovereignty, not just privacy.
256-bit AES encryption in transit and at rest, on every call, every plan — not reserved for Enterprise.
We only collect what a meeting needs to function. Nothing is retained "just in case."
Customers can ask exactly where their data sits and get a straight, documented answer — every time.
Local hosting and compliance for EU and Gulf customers, without sacrificing a single global feature.
Our founding team, working with clients across European finance and Gulf public sector projects, kept watching video vendor selection stall at the same stage: the data residency questionnaire.
Instead of retrofitting compliance onto an existing product, we started with regional data architecture — EU and Middle East hosting, encryption, and access controls — and built the meeting experience on top.
Legal, healthcare, financial services, and government teams across both regions now run their meetings on infrastructure they can actually explain to their own auditors.
Security, compliance, and infrastructure leads based in Europe and the Gulf, working alongside our core product team.
Talk to our team about data residency, compliance documentation, or a tailored security review.