This Data Processing Agreement ("DPA") is between the organization that uses Mattering under our Terms of Service (the "customer", "you") and Matt Block, Inc., doing business as Mattering ("Mattering", "we", "us"). It forms part of the Terms and applies whenever we process personal data on your behalf while providing the service. You accept it when you accept the Terms; nothing else needs to be signed.
Words such as controller, processor, data subject, personal data, personal data breach and processing mean what they mean in the GDPR. "Data protection law" means every privacy and data protection law that applies to the processing, including the EU GDPR, the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act as amended by the CPRA (the "CCPA") and similar US state laws. "Customer personal data" means the personal data we process on your behalf as part of the service.
1. Who does what
- You are the controller of customer personal data, or a processor acting for your own client. You decide what goes into your workspace, who sees it, which features process it and which services it is sent to.
- We are your processor, or your subprocessor when you act for a client of yours. If you are a processor, you confirm that your controller has authorized your instructions to us, including the use of our subprocessors.
- Your responsibilities. You are responsible for having a lawful basis for the processing, for giving people the notices and getting the consents the law requires (for example before recording a call or sending marketing texts), and for the accuracy and lawfulness of the data you put into the service.
- What this DPA does not cover. We are a controller for your account and billing details, our website, our own marketing, and the records we keep to secure the service and meet our legal obligations. Our Privacy Policy covers that data.
California and other US state laws
For customer personal data that the CCPA or a similar US state law covers, we are your service provider (and, where the law uses the term, your contractor). We process it only to provide the service described in the Terms and in Annex I. We will not:
- sell it or share it for cross-context behavioral advertising;
- keep, use or disclose it for any purpose other than providing the service, or outside our direct business relationship with you;
- combine it with personal information we receive from anyone else, except where the law allows a service provider to do so.
We will give it the level of privacy protection the law requires, and tell you if we decide we can no longer meet these obligations. You may take reasonable and appropriate steps to stop and remediate any use of it that this DPA does not allow. We understand these restrictions and will comply with them.
2. What we process
The subject matter, nature, purpose and duration of the processing, and the types of personal data and people involved, are set out in Annex I. The service is not designed for special category data (such as health data, biometric data used to identify someone, or data about racial or ethnic origin, religion, political opinions or sex life), for data about criminal convictions, or for data about children. Do not put that data into the service unless you have a lawful basis to do so and have checked that the service is suitable for it.
3. Processing only on your instructions
We process customer personal data only on your documented instructions. Your instructions are:
- the Terms and this DPA;
- how you and your users use and configure the service, including the content you add, what you share and with whom, the services you connect, and the automations and agents you build, schedule and run;
- any other written instruction we agree with you.
If we believe an instruction breaks data protection law, we will tell you. If a law requires us to process customer personal data in another way, we will tell you before we do, unless that law forbids it.
Everyone we authorize to process customer personal data is bound by a duty of confidentiality, and only people who need access to run, support or secure the service get it.
4. Security
We apply the technical and organizational measures in Annex II. We may change them as the service develops, but not in a way that lowers the overall protection of customer personal data. You are responsible for the parts of security you control: who you invite, the roles and seats you give them, what you share, the API keys you create, and the services and credentials you connect.
We do not currently hold third-party security certifications such as SOC 2 or ISO 27001, and we do not claim to.
5. Subprocessors
- Authorization. You give us general authorization to use subprocessors. The current list, with what each one receives and why, is our Subprocessors page.
- Notice of changes. Before a new subprocessor starts processing customer personal data, we will update that page and tell account owners by email or in the product at least [To be confirmed: 30] days in advance.
- Your right to object. During that notice period you may object, on reasonable data protection grounds, by contacting us as described below. We will discuss the objection in good faith and try to offer a reasonable alternative. If we cannot resolve it, you may stop using the affected feature or end the affected part of your subscription [To be confirmed by counsel: refund of prepaid fees].
- Their obligations. We bind each subprocessor by a written contract to data protection obligations that give customer personal data at least the protection this DPA requires, as far as they apply to the service it provides.
- Our responsibility. We remain responsible to you for each subprocessor's performance of those obligations, as data protection law requires.
6. Services you connect are not our subprocessors
Many features work with services your organization chooses and connects with its own account, key or sign-in: Automations connectors, your own Google or Microsoft account for Gmail, Calendar or Drive, your own email sending service or AI provider key, the voice provider key you give an agent, and your own AI assistant connected through our MCP server. These are "third-party services". They are not our subprocessors.
- Connecting a third-party service, and building or running an automation or agent that sends data to it, is your instruction to us to transfer that data to it.
- The provider of a third-party service processes the data under its own terms with you. We are not responsible for how it handles the data once it has it.
- While the data is with us on its way to or from a third-party service, this DPA still covers it. That includes the credentials we store for the connection, the inputs and outputs of automation and agent runs, their logs, and any files a run produces.
- Some features can run either on your account with a provider or on ours. When a feature runs on our account, the provider is our subprocessor and is listed on the Subprocessors page.
7. Helping you meet your obligations
- Requests from individuals. The service lets you act on most requests yourself. Your users can find, correct, export and delete content in each app. An organization owner can export the organization's data and delete the organization in its data settings, and each person can export their own data and delete their account in their account settings. Where those tools are not enough, we will help you respond, taking into account the nature of the processing.
- Requests sent to us. If someone asks us directly about customer personal data, we will pass the request to you where we can identify you and will not answer it ourselves, other than to tell the person to contact you, unless the law requires us to.
- Impact assessments and regulators. We will give you the information you reasonably need about the service for a data protection impact assessment or a prior consultation with a supervisory authority, starting with this DPA, the Subprocessors page and Annex II.
8. Personal data breaches
If we become aware of a personal data breach affecting customer personal data, we will tell you without undue delay, and in any case within [To be confirmed: 72] hours of becoming aware of it. We will notify the owners of your organization by email. As far as we know it at the time, the notice will describe:
- what happened, and the categories and approximate number of people and records concerned;
- the likely consequences;
- what we have done or plan to do about it, including steps to limit its effects;
- who to contact for more information.
Where we cannot give everything at once, we will send it in stages as we learn more. We will take reasonable steps to contain and investigate the breach. Telling you about a breach is not an admission of fault.
9. Deletion and return of data
- While you use the service, you can export and delete customer personal data at any time with the tools described in section 7. Deleted files stay in the trash for 30 days, where they can be restored, and are then removed with their versions and any search index built from them.
- When an organization is deleted, it is scheduled for deletion for 30 days. During that time an owner can cancel the deletion and export the organization's data. When the 30 days end, we erase the organization's data from every app.
- Backups. Erased data can remain in backups until they age out, within [To be confirmed: 7] days. We do not restore it from backups except to recover the service.
- What we keep. We keep customer personal data after deletion only where the law requires us to. Records we keep as a controller, such as invoices, are covered by our Privacy Policy.
- Return. Export your data before you delete your organization; the export is how we return it.
10. Audits
We will make available the information you reasonably need to show that we meet this DPA. We start with this DPA, the Subprocessors page and Annex II, and we will answer reasonable written security questionnaires.
If that information is not enough, or a supervisory authority requires it, you may audit our compliance with this DPA yourself or through an independent auditor bound by confidentiality. You must give us at least [To be confirmed: 30] days' written notice and agree the scope with us in advance. Audits are limited to [To be confirmed: 1] in any 12 months, unless a personal data breach or a supervisory authority requires another one. They take place during business hours, avoid disrupting the service, and do not give access to other customers' data. You bear the cost of the audit [To be confirmed by counsel].
11. International transfers
We host the service on Google Cloud in the United States, and some subprocessors process data in other countries, as the Subprocessors page shows. Where data protection law restricts a transfer of customer personal data out of the European Economic Area, the United Kingdom or Switzerland, these safeguards apply:
- EU Standard Contractual Clauses. The standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914 (the "SCCs") are incorporated into this DPA by reference. Module Two applies where you are a controller and Module Three where you are a processor. You are the data exporter and we are the data importer. In the SCCs: the optional docking clause in Clause 7 applies; Option 2 of Clause 9 (general written authorization) applies, with the notice period in section 5; the optional wording in Clause 11 does not apply; Clauses 17 and 18 choose the law and courts of [To be confirmed: Ireland]; Annex I of the SCCs is Annex I below, Annex II of the SCCs is Annex II below, and the list of subprocessors is the Subprocessors page.
- United Kingdom. For transfers from the United Kingdom, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner applies and is incorporated by reference. Its Tables 1 to 3 are completed with the parties, the SCC modules and options, and the annexes in this DPA [To be confirmed by counsel: Table 4 choice].
- Switzerland. For transfers from Switzerland, the SCCs apply with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for those transfers, references to the GDPR include the Swiss Federal Act on Data Protection, and people in Switzerland may bring claims in their place of habitual residence.
- EU-US Data Privacy Framework. [To be confirmed: whether Mattering will self-certify to the EU-US Data Privacy Framework, the UK Extension and the Swiss-US Data Privacy Framework. Until it is on the official list, nothing here relies on it.]
- Onward transfers. When a subprocessor receives customer personal data in a country without an adequacy decision, we use a transfer mechanism that data protection law recognizes, such as the SCCs.
If the SCCs conflict with this DPA or the Terms, the SCCs win.
12. Liability, order of precedence and term
- Liability. Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Terms, except where data protection law or the SCCs do not allow that. Nothing in this DPA limits the rights of data subjects under the SCCs.
- Order of precedence. If documents conflict, this order applies: the SCCs (where they apply), then this DPA, then the Terms.
- Term. This DPA applies for as long as we process customer personal data for you, including after the Terms end until the data is deleted as section 9 describes.
- Changes. We may update this DPA to reflect changes in the law or in the service. We will not reduce the protection it gives customer personal data, and we will tell account owners before a material change takes effect.
- Contact. For questions, objections and requests under this DPA, use our contact form, choose Support, and start your message with Privacy request. [To be confirmed: address for legal notices]
Annex I: Details of the processing
A. The parties
- Data exporter: the customer, as identified in its Mattering account. Contact: the owners of its organization. Role: controller, or processor for its own client. Activities: using the service under the Terms.
- Data importer: Matt Block, Inc., doing business as Mattering, [To be confirmed: address]. Contact: through our contact form. Role: processor (or subprocessor). Activities: providing the service.
B. People whose data is processed
Depending on which apps and features you use, customer personal data may relate to:
- your users: members, guests and people you invite;
- your contacts, leads and the people at businesses you track in Sales;
- people who email you or whom you email, when you sync a mailbox, forward or copy email to Mattering, or give an agent a mailbox;
- people on calls, meetings, phone calls and text conversations, including guests and people an agent talks to;
- people who fill in your forms, sign your contracts, book time on your calendars or scan your QR codes;
- learners and the people who coach them in Mastery;
- anyone else named or shown in the tasks, files, documents, messages, recordings or other content you add.
C. Types of personal data
- identity and contact details, such as names, email addresses, phone numbers, employer and job title;
- user account details, such as profile, role, organization and workspace membership, and sign-in records;
- content: tasks, comments, messages, files and documents, email and attachments, text messages, call audio, recordings and transcripts, notes, deals and activity history;
- form answers, with the time, IP address and browser details of each submission;
- contract signing records: signatures, signer details, one-time code checks, IP addresses, times and the audit trail;
- booking details and QR scan records (time, IP address, device, browser and approximate location);
- agent conversations, instructions and memories, and the content agents read or write;
- automation and agent run inputs, outputs and logs, and the credentials stored for connected services;
- technical data: IP addresses, device and browser details, and request logs.
Special category data: none intended (see section 2).
D. Nature, purpose and duration
- Frequency: continuous, for as long as you use the service.
- Nature: hosting, storage, backup, transmission and display; search and indexing; transcription; AI processing such as summaries, drafts, extraction, image and video generation and agent actions; sending email, texts and calls; running automations; and deletion.
- Purpose: to provide, support and secure the service for you under the Terms and your instructions.
- Duration and retention: the term of the Terms, then until deletion as section 9 describes.
- Subprocessors: the same nature and purpose, for the part of the service each one provides and for as long as it provides it. See the Subprocessors page.
E. Competent supervisory authority
The supervisory authority that Clause 13 of the SCCs points to for the data exporter.
Annex II: Technical and organizational measures
- Hosting. The service runs on Google Cloud (Cloud Run, Cloud SQL, Cloud Storage and Compute Engine) in the United States. Google Cloud encrypts stored data at rest by default.
- Encryption in transit. Traffic to the service uses HTTPS. Plain HTTP is redirected to HTTPS, browsers are told to use HTTPS only (HSTS), and sign-in cookies are marked secure and cannot be read by page scripts.
- Passwords and keys. Passwords are stored as one-way hashes (Argon2). API keys are stored as one-way hashes and shown in full only once, when created.
- Connected-account credentials. Credentials for services you connect are kept in Google Secret Manager, separate from the application database, under identifiers tied to your organization; a request for another organization's credential is refused before the secret store is contacted. Each use of a stored credential is logged with the run and person it was used for, and credential values are removed from run logs. Logins saved for agents' web browser are handed to the browser through single-use grants and never reach the AI model or the Agents app.
- Access control. Access to customer data follows organization, workspace, role and sharing permissions. Calls between our own services are authenticated with a shared internal secret, and API calls from apps and assistants you connect are authenticated with signed tokens or API keys on every request.
- Staff access. Accounts that can reach the admin tools must sign in with a password and an authenticator-app code. Repeated failed sign-ins are rate limited.
- Network protection. When the service fetches an address a customer supplies (for example in an automation's HTTP request step or a self-hosted connector), it refuses private, internal and cloud metadata addresses, checks every redirect, and connects only to the address it checked.
- Logging. Requests are logged in Google Cloud Logging. Contracts keeps an audit trail of each signing. Agent safety events are recorded.
- AI providers. We use AI providers through their business APIs. Where we have built it in, we ask a provider not to store requests; for example, Agents asks OpenAI not to store chat requests.
- Processing we run ourselves. Call and recording transcription, the relay that carries call audio and video when a direct connection fails, the web browser agents use, and document conversion run on our own Google Cloud hosting, not with another provider.
- Data lifecycle. Deleted files are kept in the trash for 30 days and then removed with their versions and search index. Audio sent for call transcription is deleted once transcribed, within 24 hours at most. Organization deletion waits 30 days and then erases the organization's data from every app. Owners can export organization data and people can export their own data from settings.
Annex III: Subprocessors
The current list is our Subprocessors page.
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. |