> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beam.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Subprocessor List

> Third parties that process data on Beam's behalf.

**Last updated:** September 14, 2026

A subprocessor is a third party that Beam engages to process Customer Data or other personal data on our behalf. This page is Schedule 3 to our [Data Processing Addendum](/v2/security/data-processing-addendum) and is referenced by our [Privacy Policy](/v2/security/privacy-policy). Each subprocessor is bound by a written agreement that imposes data protection obligations no less protective than those we owe to our customers.

## Infrastructure subprocessors

These providers host the Beam platform and process Customer Data. Workloads run in the United States by default; where the platform lets you choose another region or compute pool, your Customer Data is processed in the region you select.

| Subprocessor | Purpose | Data processed | Location |
| - | - | - | - |
| Amazon Web Services, Inc. | Cloud infrastructure: compute, storage, networking | Customer Data; account and usage data; system logs | United States (other regions where selected by the customer) |
| Google LLC (Google Cloud) | Cloud infrastructure: compute, storage, networking | Customer Data; account and usage data; system logs | United States (other regions where selected by the customer) |

## Operational subprocessors

These providers support billing, monitoring, analytics, and customer communication. They process account, usage, and support data. Customer Data may appear incidentally, for example in an error report or a support conversation.

| Subprocessor | Purpose | Data processed | Location |
| - | - | - | - |
| Stripe, Inc. | Payment processing and invoicing | Billing contact and payment details, transaction history | United States |
| Functional Software, Inc. (Sentry) | Error and performance monitoring | Error reports, which may include account identifiers, request metadata, and stack traces | United States |
| PostHog, Inc. | Product and web analytics, session replay, in-product surveys | Usage events, device and IP data, session recordings of Beam properties with all text and inputs masked, survey responses | United States |
| Google LLC (Google Analytics) | Web analytics for beam.cloud and docs.beam.cloud | Usage events, device data, approximate location | United States |
| Mintlify, Inc. | Hosting for docs.beam.cloud | Visitor IP and device data, documentation search queries | United States |
| Pylon | Customer support and in-app messaging | Support conversations, account contact details | United States |
| Slack Technologies, LLC | Shared support channels and community workspace | Messages and profile information in Beam's Slack workspace | United States |
| Loops | Account, billing, and security notifications; marketing email | Email address, name, notification content, marketing engagement | United States |

## Changes to this list

We update this page at least 30 days before a new subprocessor begins processing Customer Data, as described in Section 5 of the Data Processing Addendum, except where a provider must be replaced urgently for security or continuity reasons. To receive change notices by email, send a request to [legal@beam.cloud](mailto:legal@beam.cloud). Customers may object to a new subprocessor as described in the DPA.

Questions about this list: [privacy@beam.cloud](mailto:privacy@beam.cloud).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.