Legal

Sub-processors

Last updated October 2026

Every third party that can process your data when you use Beam, what each one does, and where it is. This list is part of the Beam SAS data processing addendum, and it is the list we keep current.

Sub-processorWhat it does with your dataEstablished in
Amazon Web ServicesThe machine this product runs on: application, database, queues and stored files.France (eu-west-3)
ClerkSign-in, sessions and workspace membership. Holds names and email addresses.United States
The model provider that answersGenerates replies, documents and summaries, so it receives the conversation and whatever it is given to work on. Anthropic, OpenAI, Google and Mistral are the providers a workspace can choose; requests reach them through the OpenRouter gateway unless the workspace supplies its own key.United States, except Mistral AI (France)
PipedreamRuns the managed connectors to your other tools and holds the authorisation to reach them.Only once somebody connects an app.United States
StripeSubscriptions, payment and invoices. Receives billing details, never workspace content.United States
ResendDelivers transactional email: invitations, notifications, password and billing mail.United States
Twilio SendGridDelivers transactional email: invitations, notifications, password and billing mail.United States
TavilyAnswers a web search with pages from the open internet. Receives the search query.Only when web search is turned on for the workspace.United States
Voyage AIReranks retrieved passages so the most relevant reach the model. Receives those passages.Only when a Voyage key is configured; otherwise reranking runs through the model gateway above.United States
SentryCollects errors so failures can be fixed. Receives diagnostic data, not workspace content.Only when error reporting is configured.United States
PexelsSupplies stock photography for generated presentations. Receives the picture search term.Only when stock pictures are turned on for the workspace.Not stated

What stays on our own machine

Beam runs on one machine in France. The database, the queue, your uploaded and generated files, the sandbox that runs code and the service that renders documents are all on it. None of them is a third party, so none of them appears above: an object you upload is written to storage on that machine, not to anybody's cloud bucket.

The providers in the table are the points where data genuinely leaves it, which is why the table is short and why we would rather it stayed that way.

What the location column means

It names the provider's principal establishment as that provider publishes it. It is not a claim about where a particular byte is stored, which is a question each provider's own terms and sub-processor list answer.

Where we have not confirmed an establishment we write "Not stated" rather than a guess. Ask us and we will get the answer from the provider in writing.

Model providers, and how to narrow them

A model provider sees what you send it: the conversation, the documents in context, the instructions your agents carry. That is the row to read first.

An administrator can restrict the workspace to a single model, so a workspace that must stay with one provider can. A workspace can also supply its own provider key, in which case the request goes to that provider directly and our gateway is out of the path, or point at a model hosted on infrastructure you control.

Changes to this list

We publish a change here before a new sub-processor starts processing customer data, and we write to the administrative contact of every workspace when one is added or replaced. If you object to an addition, tell us at legal@beamxp.com and we will work through it with you.

Beam does not train models on your data. What a provider in the table does with a request is governed by that provider's own terms, which are the document to read if it matters to you; we will point you at the current one for any row here.

Asking for more

A signed data processing addendum, the current list as a dated document, and each provider's own terms: write to legal@beamxp.com.

Questions about this document? Reach our team at legal@beamxp.com.