> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Subprocessors
> The third-party subprocessors Rootly uses to deliver its services, what each one is used for, and the categories of customer data each one processes.
## Overview
A **subprocessor** is a third party Rootly engages to process customer personal data in the course of delivering the Rootly platform. This page lists those subprocessors, grouped by the function they serve.
This list covers processing performed by Rootly. It does not cover integrations you connect yourself — see [Customer-enabled integrations](#customer-enabled-integrations) below for that distinction.
All subprocessors listed here are bound by data processing agreements. Data sent to subprocessors is used solely to provide Rootly services and is not used for model training.
***
## Infrastructure
Core infrastructure that Rootly runs on, including hosting, networking, and data transit.
| Subprocessor | Purpose | Data processed |
| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| [Amazon Web Services](https://aws.amazon.com) | Primary cloud infrastructure — compute, application databases, object storage, queuing, and event routing. Rootly runs entirely on AWS. | All customer data stored in Rootly, encrypted at rest |
| [Cloudflare](https://cloudflare.com) | Content delivery, edge networking, and web application firewall | HTTP request data and tenant identifiers |
| [ClickHouse Cloud](https://clickhouse.com/cloud) | Columnar analytics database for AI evaluation and product analytics | AI evaluation datasets and product usage metrics |
| [QuotaGuard](https://www.quotaguard.com) | Static IP proxy for outbound integration traffic | HTTP request payloads transiting to customer-connected integrations |
***
## AI Features
Applies to Rootly AI features. See [Data Privacy for AI](/ai/data-privacy-for-ai) for the full safeguards, retention terms, and bring-your-own-key options.
| Subprocessor | Purpose | Data processed |
| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| [OpenAI](https://openai.com) | LLM inference for AI-powered summarization, catchup, and generative features | Incident content submitted for AI processing |
| [Anthropic](https://anthropic.com) | LLM inference for AI-powered summarization, catchup, and generative features | Incident content submitted for AI processing |
| [Amazon Bedrock](https://aws.amazon.com/bedrock/) | Hosted model inference for AI-powered summarization, catchup, and generative features | Incident content submitted for AI processing |
| [Braintrust](https://braintrust.dev) | AI gateway and observability — LLM request routing, tracing, and evaluation | Incident content and other data submitted for AI processing |
| [Recall.ai](https://recall.ai) | Meeting orchestration, recording capture, and platform connectivity for [AI Meeting Scribe](/ai/meeting-scribe) | Meeting audio/video streams, bot lifecycle events |
| [AssemblyAI](https://assemblyai.com) (via Recall.ai) | Speech-to-text transcription, summarization, PII redaction, and speaker identification | Meeting audio for transcription |
***
## Notifications and alerting
How Rootly reaches responders when they are paged.
| Subprocessor | Purpose | Data processed |
| -------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------- |
| [Twilio](https://twilio.com) | SMS and voice call delivery for on-call paging and live call routing | Phone numbers, alert and notification content |
| [SendGrid](https://sendgrid.com) | Transactional and notification email delivery | Email addresses, notification content |
| [Mailgun](https://mailgun.com) (Sinch AB) | Transactional email delivery | Email addresses, notification content |
| [Firebase Cloud Messaging](https://firebase.google.com/products/cloud-messaging) | Push notification delivery to Android devices | Device push tokens, notification content |
| [Apple Push Notification service](https://developer.apple.com/notifications/) | Push notification delivery to iOS devices | Device push tokens, notification content |
| [Pushy](https://pushy.me) | Push notification delivery for devices in regions where FCM is unavailable | Device push tokens, notification content |
***
## Platform Operations
Tooling Rootly uses to keep the service running and reliable. These process operational telemetry, which can incidentally contain user identifiers.
| Subprocessor | Purpose | Data processed |
| ------------------------------------------------------ | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| [Datadog](https://datadoghq.com) | Application performance monitoring, logging, and infrastructure observability | Application logs and telemetry, which may include user and team identifiers |
| [Sentry](https://sentry.io) | Application error and exception tracking | Error traces and request context, which may include user and team identifiers |
| [pganalyze](https://pganalyze.com) (Duboce Labs, Inc.) | Database performance monitoring and query analytics | Database query patterns and telemetry, which may include user and team identifiers |
| [LaunchDarkly](https://launchdarkly.com) | Feature flag evaluation and progressive rollout targeting | Team and user identifiers used as targeting keys |
| [Short.io](https://short.io) | URL shortening for incident and retrospective links (root.ly domain) | Incident and retrospective URLs |
***
## Business Operations and Analytics
Internal tooling Rootly personnel use to support accounts, troubleshoot issues, and analyze product usage.
| Subprocessor | Purpose | Data processed |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| [Google Workspace](https://workspace.google.com) (Alphabet Inc.) | Corporate email, document storage, and productivity tools used by Rootly personnel | Employee and customer communication content, shared documents |
| [Segment](https://segment.com) | Customer data platform for product analytics event routing | User profile data, product usage events |
| [PostHog](https://posthog.com) | Product analytics and user behavior tracking | User and team identifiers, product usage events |
| [HubSpot](https://hubspot.com) | CRM for account management and customer communication | User profile data and account metadata |
| [Salesforce](https://salesforce.com) | CRM for account management and customer communication | User profile data and account metadata |
| [Pylon](https://usepylon.com) | Customer support platform | User profile data, support ticket content |
| [Linear](https://linear.app) (Linear Orbit, Inc.) | Internal support ticket tracking | User profile data, support ticket content |
| [Oliv.ai](https://oliv.ai) | Product and customer analytics | User profile data and product usage metrics |
| [Metabase](https://metabase.com) | Business intelligence. Rootly personnel run read-only queries against production application data to support customer accounts, troubleshoot issues, and analyze product usage. | User profile data (names, email addresses, phone numbers), incident and alert records, and associated metadata |
| [Snowflake](https://snowflake.com) | Data warehouse for aggregated product usage and account health analytics | Product usage metrics and account metadata |
| [Stripe](https://stripe.com) | Subscription billing and payment processing | Billing contact details and payment metadata |
***
## Communication and support
How Rootly personnel communicate internally and with customers.
| Subprocessor | Purpose | Data processed |
| ---------------------------------------------------- | ----------------------------------------------------- | ----------------------------------------------- |
| [Slack](https://slack.com) (Slack Technologies, LLC) | Internal team communication and incident coordination | User identifiers, message content |
| [Intercom](https://intercom.com) (Intercom, Inc.) | In-app live chat and customer support | User profile data, support conversation content |
***
## Customer-Enabled Integrations
Rootly connects to a wide range of third-party tools — Microsoft Teams, Jira, PagerDuty, GitHub, Datadog as an alert source, and [many others](/integrations/overview).
These are **not** Rootly subprocessors. You enable them, you control the credentials, and data flows to them at your direction under your own agreement with that vendor. Rootly acts on your instruction to send data to a destination you chose.
The distinction matters for your own DPA: the vendors listed above process your data because Rootly engaged them. Integration vendors process your data because you did.
***
## Changes to this list
Rootly maintains a data processing agreement covering the processors listed here. To request the current DPA, or to ask about notification of changes to this list, contact your account team or [security@rootly.com](mailto:security@rootly.com).
Additional compliance artifacts — SOC 2 Type II report, penetration test results, and security policies — are available through the [Rootly Trust Center](https://security.rootly.com).