Murmurly Subprocessors
Murmurly uses selected third-party service providers to help provide, secure and operate the Services. Where a provider processes Customer Personal Data on Murmurly’s behalf, that provider acts as a subprocessor.
This page lists Murmurly’s current subprocessors and provides information about the purpose and location of their processing.
Last updated:
Data regions
Each Customer’s data is processed according to the Customer’s configured deployment region. Murmurly currently supports EU and US data regions.
The processing locations shown below follow that region and, for some providers, the service or functionality used.
Current subprocessors
-
Convex
- Purpose
- Application backend, database, data storage and processing
- Data processed
- Customer Personal Data stored in or processed through the Murmurly platform
- Processing location
- EU or US, depending on the Customer’s configured deployment region
-
Amazon Web Services (AWS)
- Purpose
- Cloud infrastructure, storage, content delivery, email delivery and related infrastructure services
- Data processed
- Customer Personal Data processed through the applicable AWS services, including communications and related delivery information where applicable
- Processing location
- EU or US, depending on the Customer’s configured deployment region and the applicable AWS service
Additional service-dependent processing locations may apply.
-
Google Cloud
- Purpose
- AI processing, including generative and conversational AI, embeddings, summarisation and real-time speech functionality
- Data processed
- Prompts, messages, notes, contextual information, Customer Personal Data made available to AI Features, audio, speech and related data
- Processing location
- EU or US, depending on the Customer’s configured deployment region and the applicable AI functionality
For EU deployments, server-side text-based AI and embeddings are processed on EU-configured Google Cloud infrastructure. Real-time speech uses a direct client connection to Google Cloud and is not subject to a specific data residency commitment by Murmurly; it may be processed outside the EU.
Optional integrations
Customers may choose to connect Murmurly to supported third-party services.
A provider of an optional integration is not automatically a Murmurly subprocessor solely because a Customer chooses to connect that service.
Where an integration provider processes Customer Personal Data on Murmurly’s behalf, it will be treated as a subprocessor and included on this page where applicable.
Where the provider processes Personal Data under a direct relationship with the Customer, the applicable terms and data protection arrangements of that provider apply.
Changes to this list
Murmurly may add or replace subprocessors from time to time.
In accordance with the Murmurly Data Processing Addendum , Customers will receive written notice of an intended addition or replacement of a subprocessor at least fourteen (14) days before that provider is authorised to process Customer Personal Data.
Customers may object to an intended addition or replacement on reasonable grounds relating to the protection of Customer Personal Data, by notifying Murmurly in writing within fourteen (14) days after receiving that notice, in accordance with the Data Processing Addendum.
For questions or objections, contact legal@murmurly.io .