Braid

Sub-processors

Last updated 25 August 2026

Braid uses the companies below to deliver the service. Each processes personal data on our behalf, under contractual terms that oblige them to protect it. This list is referenced by our data processing agreement.

Infrastructure

Sub-processorWhat it doesData involved
SupabaseThe database, authentication and file storage behind Braid. Workspace data lives here.Everything: account data, conversations, contacts, knowledge, files
VercelHosts and serves the application.Request metadata, IP addresses
Amazon Web ServicesInbound and outbound email for the email channel. Inbound message bodies are held in object storage while being processed.Email content, sender and recipient addresses

AI

Sub-processorWhat it doesData involved
AnthropicGenerates the agent's replies.Conversation content and the knowledge passages retrieved to answer it
OpenAITurns your knowledge and incoming questions into embeddings, so retrieval can find the right passage.Knowledge content, question text

Neither trains foundation models on data we send them; both process it to return a result and nothing more.

Messaging platforms

Sub-processorWhat it doesData involved
Meta PlatformsDelivers WhatsApp and Instagram messages in both directions.Message content, phone numbers, account identifiers, profile names

Meta is unavoidable for these two channels — it is the channel. If you do not connect WhatsApp or Instagram, no data reaches Meta through Braid.

Where data is held

Workspace data — conversations, contacts, knowledge and files — is stored and processed in the European Union.

Some sub-processors above are established outside the EU. Where personal data reaches them, the transfer relies on the European Commission's Standard Contractual Clauses or an adequacy decision.

Changes

We will update this page before adding a sub-processor that processes customer personal data, and notify workspace admins. If you object to a new sub-processor, write to privacy@getbraid.ai — the objection procedure is in our DPA.