These are the third-party providers that process personal data on our behalf to run Mattering. For each one we list what it receives and why. Our Privacy Policy explains the rest, and our Data Processing Agreement sets out how we use subprocessors for customer data.
Before a new subprocessor starts processing customer personal data, we update this page and tell account owners by email or in the product at least [To be confirmed: 30] days in advance. Your organization can object during that time, as the Data Processing Agreement describes. For questions, use our contact form, choose Support, and start your message with Privacy request.
Hosting, storage, email and payments
| Provider | What it receives | Why |
|---|---|---|
| Google Cloud (United States) | All account data and workspace content, including files, recordings and transcripts, stored credentials, automation and agent runs, and logs | Hosting, databases, file storage, the secret store for connected-account credentials, request logs, and the servers that run call transcription, the call relay, agent voice and the agents' web browser |
| Stripe | Organization name, the billing user's email, plan and subscription details, and the card or payment details you enter on Stripe's pages | Payments, subscriptions and invoices |
| Mailgun | Recipient email address and the content of the email we send; for Sales email logging, the full content of email that people forward or copy to their Mattering logging address, including the other people on it | Sending service email, such as password resets, invitations and contract signing requests, and receiving email for Sales email logging |
| Twilio | Phone numbers, call audio and text messages, and call recordings or voicemail when your organization turns them on | Mattering phone numbers, calls and texts |
| Google (STUN) | Your IP address and network port when a call starts | Helping call participants connect to each other |
AI providers
These receive content only when someone uses an AI feature. See How we use AI.
| Provider | What it receives | Why |
|---|---|---|
| Anthropic | Prompts, conversation history, agent instructions, and the app content, files, images and transcripts a feature needs, including email from a connected Gmail account that an agent reads | Matter and other agents, the in-app chat panel, Comms summaries and reply drafts, the Productivity assistant, the Mastery tutor, and AI steps in automations |
| OpenAI | Chat content, including email from a connected Gmail account that an agent reads, when an organization selects an OpenAI model; text from files added as knowledge; live call speech and reply text for agents that speak with our OpenAI voice, including when another voice provider stops working during a call; image prompts | Optional chat models, the knowledge search index, agent voice, and image generation |
| Google (Gemini) | Chat content, including email from a connected Gmail account that an agent reads, when an organization selects a Gemini model; text from files added as knowledge when a Gemini search model is used; image prompts and reference images | Optional chat models, the knowledge search index, and image generation |
| Black Forest Labs, fal, Runway, Luma | Prompts and reference images | Image and video generation, depending on the model chosen |
| Higgsfield | Prompts and input images | Image and video generation in video steps, when a step runs on our account |
| DataForSEO | Keywords, domains and business names | Search data for SEO and research steps, when a step runs on our account |
Image and video generation, DataForSEO and Higgsfield can also run on your organization's own account with the provider. When they do, that provider is a service you connect (below), not our subprocessor.
Website and delivery networks
| Provider | What it receives | Why |
|---|---|---|
| Google Analytics | Pages viewed, IP address and browser details. On our website, only if you accept analytics cookies | Measuring website and product use |
| Google Fonts, cdnjs (Cloudflare), jsDelivr, code.jquery.com, cdn.datatables.net | IP address and browser details when your browser loads a font, icon set or code library | Delivering page assets |
Services you connect
When your organization connects a service with its own account, key or sign-in, data moves between Mattering and that service because you asked for it. Examples are Automations connectors such as Slack, Notion or GitHub, the Google or Microsoft account you connect for Gmail, Calendar or Drive, your own email sending service or AI provider key, the ElevenLabs or OpenAI key you give an agent for its voice, and your own AI assistant connected through our MCP server. Those services are chosen by your organization and process the data under their own terms with you, so they are not listed above. Connecting one, and running an automation or agent that sends data to it, is your instruction to send that data there. While the data is with us on its way, including the credentials we store, run inputs and outputs, logs and files a run produces, our Data Processing Agreement still covers it. What we do with data from Google is described in our Privacy Policy.
What we run ourselves
Some processing that often goes to a third party runs on our own Google Cloud hosting instead: speech-to-text for Comms calls and Productivity recordings, call recording processing, the relay that carries call audio and video when a direct connection fails, the web browser agents use, document conversion and editing, video rendering, and the tools that read and capture web pages for automations and agents.
Changes to this page
We will update this page when our practices or the law change. When a change is material, we will tell account owners by email or in the product before it takes effect. The effective date at the top always shows the current version.
| Date | Change |
|---|---|
| November 15, 2026 | Data Processing Agreement published. Subprocessors: email forwarded or copied to Mattering for Sales email logging, where we host data, notice of new subprocessors, and ElevenLabs moved to services you connect. Terms: link to the Data Processing Agreement. |
| November 15, 2026 | Terms: rules for email outreach sent from your own mailbox, and prior consent for marketing texts and calls. Privacy Policy: what we receive from Google, including Gmail, and how it is used. Subprocessors: email that agents read. |
| November 11, 2026 | First published version of these pages. |