Who processes your data

13 companies are in the meeting-data path — 5 in the EU, 5 in the United States, and 3 inside your own tenant, where we hold no copy. A further 6 are listed at the end and cannot be reached from the meeting product — our own research tools, and the tag that counts responses to our advertising on the public pages. They are named so this page can be checked against our whole codebase rather than only the flattering part.

It is generated from our source code, not written by hand. An earlier version was maintained by a person and drifted: it named tools we had stopped using, gave the wrong region for our database, and missed a company that had been in the audio path for nine days.

So the mechanism is a test rather than a habit. Our build fails if our software contacts a company this page does not name. A new sub-processor cannot reach production without appearing here first.

Notice before we change it. We will tell you before a new company joins this list where your agreement with us requires it. If you would like to be told regardless, write to [email protected] and we will add you.

Optional action counts and company tags. No meeting content or screen recordings. Withdraw through Analytics settings.

Each one receives meeting content in the ordinary course of the product working.

Reached only when someone turns the notetaker on. No bot joins a meeting by default, and an organisation-level switch overrules every host.

Connected with your own credentials, under your own agreement with that provider. We read meeting times, titles and who is invited.

Reached when somebody reports a problem, not in the course of a meeting.

Reached only from the program's pay page, by an accepted applicant paying their own fee. Receives what a card payment needs and nothing about any meeting.

Reached only on our public marketing pages, before anybody signs in. It is held off every meeting link and every signed-in screen by an allowlist our build checks, because on those pages the web address itself is a key — so an advertising tag loading there would hand one over.

Listed for completeness and declared out of scope: these read public web sources for our own sales work. No meeting content, no participant and no uploaded document ever reaches them.

The hardest kind of sub-processor to find is one we hold no account with and no credential for — a setting inside another company's product that selects a third. We never contact such a party directly, so neither a credential audit nor a network audit finds it. This is where we declare them.