Our subprocessors
To provide our services, we use third-party service providers (referred to as "Subprocessors") who may process Customer Data. This page provides an overview of these Subprocessors and the purpose for which they process data on our behalf.
We perform a due diligence review of all Subprocessors to ensure they meet our security and privacy standards. This includes reviewing their SOC 2, ISO 27001, or other relevant security reports. We also have a Data Processing Addendum (DPA) or similar agreement in place with each Subprocessor.
This list may be updated from time to time. We will provide at least 30 days' notice of any new Subprocessors that we intend to use for processing Customer Data.
Last Update - September 8, 2025
Subprocessor Name |
Purpose |
Data Processed |
Location |
Amazon Web Services (AWS) |
Cloud infrastructure and hosting provider for core services. |
Customer data, application logs, and backups. |
USA |
Google Cloud Platform (GCP) |
APIs, LLMs |
Input prompts, text data, user-generated content. |
USA |
Microsoft Azure |
AI, ML and Data Lakehouse |
Customer data, data sets for AI/ML models and analytics. |
USA |
OpenAI |
AI models for our application's AI-powered features. |
Input prompts, user queries, and any data provided to the model to process. |
USA |
Datadog |
Logging and Monitoring |
Application Logs |
USA |
Jira |
Project Management |
Customer support tickets, project tasks, and internal team data. |
USA |
Microsoft 365 |
Exchange, Sharepoint, Teams |
Internal emails, documents, and communications that may contain customer data. |
USA |
Port Key |
LLM Gateway, LLM Monitoring and Observability |
LLM prompts, model responses, and related metadata. |
USA |