Snapshot 49611
Normalized text
Scripts and page chrome removed; this is what change detection compares.
To support the provision of our services, meetergo GmbH ("meetergo") may engage and employ data processors ("sub-processors") with access to certain personal data. On this page, you will find important information about the identity, location, and role of each sub-processor we use.
Terms used on this page but not explicitly defined have the meanings given in our Terms of Service or the Data Processing Agreement (DPA) entered into with you, the customer. If you are a customer of meetergo and would like to receive the additional DPA, please log into your account and download it under Settings → Legal & privacy → Compliance documents. See GDPR documents: download your DPA, privacy snippet and confidentiality agreement (NDA).
The information provided here is to inform you about how meetergo collaborates with third-party systems, particularly which providers we use in the provision of the meetergo service for you. This should not be interpreted as an offer of additional rights or binding agreements.
How do we protect your data?
We take the protection and security of your personal data very seriously and have strict procedures in place to ensure that this information is secure and only shared when necessary.
Booking Page Third-Party Cookies: We do not allow third-party cookies to be embedded on the booking page. It is free from cookies.
Personal Information: We use Secure Socket Layer (SSL) technology when collecting, storing, and processing all data. Access to all accounts is via secure login with one-way hashing of all passwords. We do not access or share data unless we are legally required to do so or have your permission to fix system issues.
Payments: All transmitted sensitive data/credit information is transferred using Secure Socket Layer (SSL) technology and then encrypted in the database of our payment gateway provider, so that only those with special access rights to these systems can access it, and they are required to keep the information confidential. We do not store this information ourselves but rather with our payment providers who meet the highest PCI compliance standards.
meetergo also requires all third-party vendors or sub-processors we use in the provision of this service to you to comply with the requirements and obligations under GDPR as well as the requirements of the local authority (DE).
Third Parties (Sub-processors)
We have divided the list of processors into relevant sections so that you better understand how these services access your data.
Each entry lists the legal entity (this is what our data processing agreement with the provider is signed with), the storage/processing location (where your personal data actually lives), and, if the legal entity is based in a third country outside the EU/EEA, the transfer mechanism we rely on under Chapter V of the GDPR. "SCCs" refers to the European Commission's Standard Contractual Clauses (2021/914). "EU-US DPF" refers to the EU-US Data Privacy Framework (adequacy decision of 10 July 2023). The United Kingdom and Switzerland benefit from their own adequacy decisions, so no additional transfer mechanism is required.
Infrastructure Sub-processors - Service Data Storage
meetergo uses the following organizations to store/host/collect personal data or provide other infrastructure that helps with the provision of the meetergo service. These are secure environments controlled by the meetergo team and protected by data processing agreements:
Name of Entity Purpose Storage / Processing Location Third-Country Transfer Mechanism
OVH SAS (OVHcloud) Website hosting EU (France) Not applicable (EU entity, EU processing)
Hetzner Online GmbH Cloud infrastructure, hosting, storage; user identity and authentication (self-hosted); real-time video and audio servers for meetergo Connect and the AI phone assistant Germany (Falkenstein, Nuremberg) Not applicable (EU entity, EU processing)
BunnyWay d.o.o. (bunny.net) Content delivery network (static assets, images) Global CDN, primarily EU edge nodes Not applicable (EU entity, EU-established group)
Service-Specific Sub-processors
meetergo works with other third-party vendors to provide specific functions or features within the meetergo service. These vendors have access to relevant personal data (both identifiable and anonymous) to provide their respective functions. The use of the information is limited to the purposes listed below:
Name of Entity Purpose Storage / Processing Location Third-Country Transfer Mechanism
Stripe Payments Europe Ltd Cloud-based billing services for the meetergo subscription EU (Ireland) contracting entity; onward transfers to Stripe, Inc. in the United States for fraud prevention and global payment infrastructure SCCs (2021/914); EU-US DPF (Stripe, Inc. is DPF-certified)
Crisp IM SAS Cloud-based customer support EU (France) Not applicable (EU entity, EU processing)
AhaSend B.V. Transactional email delivery (booking confirmations, reminders, account notifications), receipt of inbound support email sent to a meetergo support address, and routing of supplier documents sent to a company's assigned bills and receipts address Netherlands Not applicable (EU entity, EU processing)
Mistral AI SAS AI features (the Mira assistant, Calgent booking assistant, AI-assisted meeting-type and form creation, knowledge-base embeddings, AI phone assistant); invoked only when you enable or use these features. Mistral does not use the data for training and keeps requests and responses for at most 30 days for abuse monitoring. EU (France) Not applicable (EU entity, EU processing)
melious GmbH EU-hosted open-weights model inference for AI features (including the Mira assistant, AI-assisted creation, summaries, AI phone assistant); invoked only when you enable or use these features. Prompts are not retained beyond the request. Germany Not applicable (EU entity, EU processing)
Twilio Ireland Limited Cloud-based SMS messaging (booking reminders, confirmations, and workflow-triggered messages) sent through meetergo's own account EU (Ireland) contracting entity; onward transfers to Twilio, Inc. in the United States as sub-processor SCCs (2021/914); EU-US DPF (Twilio, Inc. is DPF-certified)
Friendly Captcha GmbH Anti-spam protection for selected forms and booking pages, loaded only where we or a meetergo user has activated this protection. Processes the requester's IP, user-agent, referrer and timestamp to distinguish humans from automated submissions. Germany Not applicable (EU entity, EU processing)
HeyJobs GmbH (Join) Applicant-tracking system used to receive and manage job applications submitted via meetergo's careers page. Processes only applicant data (CV, cover letter, contact details); not used for meetergo customer or booking data. Germany Not applicable (EU entity, EU processing)
AI Phone Assistant (only when you use it)
The providers below process data only when your company uses the AI phone assistant. Without a configured assistant, no data flows to them. Processing in the EU is the default. We name every provider that is based or processes data outside the EU, together with its transfer mechanism. Data categories, retention and your settings are described in AI phone assistant: privacy information.
Default: processing in the EU
These providers process every call of an active assistant, including browser test calls.
Entity Name Purpose Storage / Processing Location Transfer Mechanism (Third Country)
Gladia SAS Speech recognition: turns the caller's speech into text EU (France) Not applicable (EU entity, EU processing)
Mistral AI SAS Language model that generates the replies during the call, and search in company knowledge EU (France) Not applicable (EU entity, EU processing)
Gradium SAS Speech output: turns the assistant's replies into speech EU (France) Not applicable (EU entity, EU processing)
melious GmbH Call summary after the call ends. If melious is unavailable, Mistral AI SAS takes over. Germany Not applicable (EU entity, EU processing)
The call connection, the call log and notifications run on Hetzner Online GmbH and AhaSend B.V., listed above.
Phone number: named explicitly
Entity Name Purpose Storage / Processing Location Transfer Mechanism (Third Country)
Telnyx LLC Provides the phone number, routes calls to meetergo and verifies the number holder's details (address, documents) Calls: Europe region, voice data via Frankfurt (Germany); account data: storage location Germany; contracting entity in the USA SCC (2021/914); EU-US DPF (Telnyx LLC is DPF-certified)
Telnyx is used only when you order a phone number for the assistant through meetergo. The number is registered to your company, so Telnyx receives the number holder details this requires. The EU settings determine how calls are routed. They do not guarantee that Telnyx performs all other processing, such as support or call records, in the EU.
Only on your explicit choice: processing in the USA
The providers below receive data only when you explicitly select a voice for an assistant that is labelled with the region USA in the voice picker. None of these voices is preselected. Without that choice, these providers receive no data.
Entity Name Purpose Storage / Processing Location Transfer Mechanism (Third Country)
Eleven Labs Inc. Speech output for ElevenLabs voices. Receives the text of the assistant's replies, which can contain details from the call. Speech recognition and the language model stay in the EU. USA SCC (2021/914)
OpenAI Ireland Ltd Real-time speech model for the voices Marin and Cedar. Processes the whole conversation: the caller's speech and the replies. Currently available only when enabled by meetergo. Contracting entity in the EU (Ireland); processing by OpenAI group companies in the USA SCC (2021/914)
Integration Partners (distinct from sub-processors)
The meetergo platform offers the technical ability to extend its functionality with selected integration partners (for example, your calendar provider, your CRM, or a conferencing tool). The functionality provided by that integration partner is the responsibility of the respective third party, and the associated data processing is your responsibility as the customer. You are the controller for that processing and enter into the relevant licence and data processing agreements directly with the integration partner. When you authorise a data transfer to a partner (typically by connecting your own account via OAuth or an API key), meetergo transmits the relevant data to that partner on your instruction.
For this reason, integration partners are not meetergo's sub-processors. The list below is provided for transparency so you can see which partners meetergo can connect to. Transfer mechanisms, processing locations, and retention periods for data on those platforms are governed by your agreement with each partner.
Integration Partner Category
HubSpot, Inc. CRM
Salesforce.com, Inc. CRM
Pipedrive OÜ CRM
Elastic Inc. (Close, dba Close.com) CRM
SmartWe World SE (SmartWe), CAS-Weg 1–5, 76131 Karlsruhe, Germany CRM
Ameise Software (webEdition GmbH) CRM
SC-Networks GmbH (Evalanche) Marketing automation
KlickTipp Limited Email marketing / marketing automation
GetResponse S.A. Email marketing / marketing automation
Linkando GmbH Workshop / event management
Google LLC (Google Calendar, Google Meet) Calendar and conferencing
Microsoft Corporation (Outlook Calendar, MS Teams) Calendar and conferencing
Apple Inc. (iCloud Calendar) Calendar
Zoom Video Communications, Inc. Conferencing
Cisco Systems, Inc. (Webex) Conferencing
Infomaniak Network SA (kMeet) Conferencing
Zapier, Inc. Workflow automation
Aircall SAS Phone
Slack Technologies, Inc. Communication / notifications
Meta Platforms Ireland Limited (WhatsApp Business Platform) Messaging (connected via your own WhatsApp Business account)
Superchat GmbH Messaging (connected via your own Superchat account)
External Communication Channels (not sub-processors)
meetergo maintains a presence on third-party communication channels so that users can reach us there. These platforms are independent controllers of any data you share with them when you use them - they are not meetergo's sub-processors under Art. 28 GDPR, and they do not sign meetergo's data processing agreement. When you contact us through one of these channels, you are additionally subject to that platform's own privacy terms.
If you send us information through one of these channels and we subsequently process it for meetergo purposes (for example by continuing the conversation via our customer support tools), the corresponding meetergo-internal processing is governed by the service-specific sub-processors listed above.
Platform Operator Processing location
Facebook, Instagram Meta Platforms, Inc. USA
X (Twitter) X Corp. USA
Changes and Updates
As our company grows and evolves, the third parties and sub-processors we work with may change over time. We will inform the account holder of any changes by sending a notification to the registered account holder's email address and posting any changes here. Please check here to stay up to date.
Was this article helpful?
Let us know if this article answered your questions.
Related articles
AI phone assistant: privacy informationWhich data the AI phone assistant processes per call, which providers are involved, where the data is processed and how long it is kept. Input for your data protection impact assessment.
Double Opt In (DOI)Learn how to enable Double Opt-In for GDPR-compliant booking confirmations and export audit trails for legal evidence.
GDPR documents: download your DPA, privacy snippet and confidentiality agreement (NDA)Where to find the data processing agreement (DPA), the privacy policy snippet and the § 203 StGB confidentiality agreement (NDA) for lawyers, doctors and tax advisors, how to delete booking data automatically, and why a cookie scanner finds entries on your booking page.
Withdrawal button (§ 356a BGB)Set up the statutory withdrawal function for paid consumer bookings, mandatory in the EU since 19 June 2026.