Sub-processors

Last Updated: 2 July 2026

MeetDoris Ltd (trading as DorisLabs) engages a small set of sub-processors — third-party providers that process customer content on our behalf — to deliver the Doris services. This page is the current list. Where our customer agreements require it, we give customers advance notice of new sub-processors so they can object; to receive change notifications, email privacy [at] meetdoris [dot] com.

Sub-processor Purpose Customer content processed Primary processing location
Microsoft Azure
Microsoft Corporation
Cloud hosting, compute, storage, and databases Full platform data United Kingdom (Azure UK South)
Azure-hosted model endpoints (e.g., Azure OpenAI Service)
Microsoft Corporation
AI inference Meeting content submitted for inference United Kingdom (Azure UK South); United States (Azure US East) where required for model availability, unless UK/EEA-Only Processing is enabled for a customer
Attendee
Attendee Inc.
Meeting-bot infrastructure — joins Zoom, Microsoft Teams, and Google Meet meetings to capture audio and produce structured transcripts Meeting audio, meeting platform attendee metadata, transcribed text United States
Deepgram
Deepgram Inc.
Speech-to-text transcription (engaged via Attendee) Meeting audio submitted for transcription United States by default; European Union endpoint where UK/EEA-Only Processing is enabled for a customer
Auth0
Okta, Inc.
Authentication Identity and access metadata (user identifiers, authentication events) United Kingdom / European Economic Area (tenant-dependent)
Help Scout
Help Scout, Inc.
Customer support desk Support ticket content and requester identity/contact data United States
Sentry
Functional Software, Inc.
Error tracking and performance monitoring Exceptions and traces (minimized), diagnostic event data European Economic Area, where configured

"Primary processing location" reflects configuration and typical operation. Some vendors may involve global support or onward processing; where that results in restricted international transfers, appropriate safeguards (such as the UK IDTA and/or EU Standard Contractual Clauses) apply under our customer agreements.

Independent providers (not sub-processors)

Some providers process personal data for their own purposes as independent controllers rather than on our behalf — for example, Stripe (payments), which handles payment data under its own privacy policy and legal obligations.

Integrations you connect (not sub-processors)

Calendar, email, CRM, and meeting platforms our customers choose to connect — such as Google Workspace, Microsoft 365, HubSpot, Zoom, Microsoft Teams, and Google Meet — are governed by the customer's own agreements with, and configuration of, those providers. They are not our sub-processors; we exchange data with them at the customer's direction.

Questions

For questions about our sub-processors or data practices, see our Privacy Policy or contact privacy [at] meetdoris [dot] com.