Subprocessors
Emcie uses the service providers below to support the production Parlant services. This page should be read with our Data Processing Addendum, Privacy Policy and AI Terms.
A subprocessor processes personal data on our behalf when we provide services to a customer under the Data Processing Addendum. A provider may also process information for other purposes, such as account administration or billing. We distinguish those uses below.
The information each provider receives depends on the features used and the information submitted. Listing a provider does not mean that it receives every customer's data or every conversation.
Hosting, storage and AI services
| Provider and service | Purpose | Data processed for the service | Provider information |
|---|---|---|---|
| Google Cloud, including Firebase, Firestore and Vertex AI | Platform infrastructure, managed hosting, storage and supporting AI services. Vertex AI supports Lighthouse embeddings, answer processing and evaluation. | Hosted customer and project data, conversations, application records, logs and build artifacts; relevant Lighthouse questions, context, answers and embeddings. | Cloud Data Processing Addendum |
| Google Gemini API | Session titles and summaries, Coparlant and our website agents. This API is separate from Vertex AI. | Relevant conversation text, questions, prompts and the agent, session or tool context needed by the feature. | Gemini API terms |
| MongoDB Atlas | Platform and observability databases, managed-project databases and session search. | Customer, project and session records, conversation data, traces, logs and search text and embeddings, according to the service used. | Data Processing Agreement |
| Anthropic API | Inspection of connected repositories for managed deployment, and Lighthouse documentation answers. | Selected repository files and configuration for inspection; Lighthouse questions, context and relevant documentation passages. | Data Processing Addendum |
The AI Terms describe the individual AI features and their data flows. A model provider whose account or key a customer connects to their own agent is not our subprocessor merely because the customer uses that provider.
Operational support services
The following providers support security, monitoring, incident handling and email. When these activities involve personal data processed on a customer's behalf, the providers act as subprocessors for that processing. Our processing for our own account, support and administration purposes is described in the Privacy Policy.
| Provider and service | Purpose | Information involved | Provider information |
|---|---|---|---|
| Cloudflare | Traffic delivery, edge security and network protection. | IP addresses, request and network metadata, and traffic passing through the configured service. | Data Processing Addendum |
| Grafana Cloud | Operational logging, tracing and monitoring. | Application and runtime logs, traces, identifiers and diagnostics. Logs and traces may contain customer content. | Data Processing Agreement |
| incident.io | Production alerts and incident handling. | Alert descriptions, affected services, timestamps and diagnostics included in alerts or incident records. | Data Processing Agreement |
| Google email services | Delivery of platform emails and handling of support and privacy correspondence. | Sender and recipient details, email content and information included in a request or notification. | Google Privacy Policy |
Other providers and customer-connected services
These services have different purposes from processing customer data under the Data Processing Addendum:
- Microsoft Clarity provides dashboard usage analytics and session replay under the choices and regional rules described in our Privacy Policy. This concerns Emcie's analytics of platform use. Microsoft Clarity privacy information.
- Stripe processes payments, subscriptions, invoices and related billing information. Its role depends on the processing activity; listing it here does not classify all Stripe processing as customer-data subprocessing. See our Privacy Policy and Stripe's Data Processing Agreement.
- GitHub provides repository connections and delivery tools. A customer authorizes access to selected repositories and branches for managed deployments. Customer-selected repository hosting is distinct from services Emcie obtains to deliver the platform. GitHub customer agreements and data protection terms.
- DB-IP supplies the downloaded database used for approximate IP-based location lookups. Those lookups run locally in our services; the lookup does not send the visitor's IP address to DB-IP. DB-IP database information.
Processing locations
Our production Google Cloud hosting and Firestore storage are configured in the United States, in the us-east4 region. This does not mean that every provider's model processing, support, backups or other services are confined to that region.
The standard service does not promise processing exclusively in a particular country or region. International transfers are governed by Section 9 of the Data Processing Addendum; any separate signed Enterprise agreement applies as provided in that agreement.
Changes and questions
Section 8 of our Data Processing Addendum governs subprocessor appointments, including prior written notice and customers' rights to object. Updating this page does not replace those notice requirements.
For questions about this list or the processing of personal data, contact [email protected].
Last updated: November 1, 2026.