This policy explains what personal data Mattering collects, why we collect it, who else receives it, and the choices you have. It covers the website at mattering.io, the Mattering account and sign-in service, and the Mattering apps (for example Productivity, Automations, Agents, Comms, Contracts, QR, Calendar and Files). Forms and Sales are coming soon; when they are available to you, this policy covers them too.
In this policy, "Mattering", "we" and "us" means Matt Block, Inc., doing business as Mattering. "You" means a visitor to our website, a person with a Mattering account, or a person who interacts with a Mattering customer through one of our public pages.
Two roles: our own data, and data we hold for customers
For your account, your billing, our website and our own marketing, we decide how the data is used. We are responsible for it.
Most of what lives inside Mattering is different. When an organization puts content into its workspace (tasks, files, messages, contacts, contracts, form responses, bookings, recordings), that organization decides what to collect and why. We process that content on its behalf and on its instructions. If you filled in someone's form, signed someone's contract, booked time on someone's calendar or scanned someone's QR code, the organization that sent it to you is the right first contact for questions about your data. We will help them answer you.
What we collect
When you create and use an account
- Account details: your name, email address, phone number (asked for at sign-up), password (stored only as a one-way hash, never in readable form), optional profile photo, and your time zone. If you let it, your browser reports your time zone so times show correctly.
- Organization and access: the organizations, teams and workspaces you belong to, your role in each, the apps and seats assigned to you, invitations you send or receive, and whether you use multi-factor sign-in.
- Sign-in and security records: each time you sign in, use a session, or an app or API key acts for you, we record the IP address, the browser's user agent, a short device code calculated from your browser's headers, and the time. We also record failed sign-ins and token events. We use these to keep accounts secure, spot misuse and investigate problems.
- How you got here: if you agreed to analytics cookies on our website, we keep the page you first landed on, the referring site, any campaign tags in the link (such as utm tags), and the last few pages you visited before signing up. We save this with your account to understand which pages and campaigns bring people to Mattering.
- Product records: which onboarding steps you have completed, and usage counts such as AI credits and automation runs, which we need to apply plan limits and bill correctly.
When you pay
Payments are handled by Stripe on pages Stripe hosts. We store your organization's Stripe customer reference, plan, subscription, invoice history and usage. We do not receive or store full card numbers.
Content you and your organization add
This is whatever you put into the apps, including: tasks, projects, notes, comments, goals and time entries; files and their versions; messages, reactions and attachments in Comms; audio and video recordings and their transcripts; contacts, companies, deals, notes and email in Sales; contracts, signature images and signing records; forms and their responses; booking pages and bookings; QR codes and their scan records; conversations with Matter and other agents, agent memories and agent schedules; automations, their run history, and data you keep in Databases.
Some of this content is about other people, such as the contacts in a CRM. The organization that adds it is responsible for having the right to do so.
Calls and recordings
- Comms calls are transcribed. During a Comms call, each participant's browser sends short slices of their own microphone audio to our servers, where our own speech-to-text software (running on our hosting, not a third-party AI service) turns it into text. The transcript is kept. The audio slices are deleted once transcribed, and any left over are deleted within 24 hours.
- Recordings are a separate choice. A member can start a recording, or a workspace can turn on automatic recording. Everyone on the call, including guests, sees a recording indicator. Recordings (audio, camera and screen) are saved as files in the organization's file library.
- Phone calls and texts. If your organization uses Mattering phone numbers, our telephony provider carries the calls and texts. If your organization turns on call recording or voicemail, the recording is stored by that provider and we keep a link to it.
Connected accounts
If you connect another service (for example Google, Microsoft, Slack, Notion or GitHub), we store the access token or key that service gives us, encrypted, in a dedicated secret store. We record each time a stored secret is used. We read and write data in that service only to do what you or your automations and agents ask. Google connections, including Gmail, are described in Information we receive from Google.
If you use our public pages without an account
Mattering customers use our pages to reach you. Depending on the page, we collect:
- Forms: the answers you give, plus your IP address, browser user agent and the page that linked to the form, which help the form owner spot spam and abuse.
- Contract signing: your name and email as entered by the sender, when you viewed, signed or declined, your consent to sign electronically, your signature image and the values you enter, and the IP address and user agent of each step. This audit trail is what makes an electronic signature verifiable, so it is kept with the contract.
- Calendar bookings: your name, email, time zone, any notes you add, and other attendees you name.
- QR codes and short links: when you scan or open one, we record the IP address, user agent, referring site, your device type, browser and operating system, and your approximate country and region. The country and region come from our hosting provider's network, not from your device's location.
- Guest calls: the name you enter and your audio and video during the call, which is transcribed as described above.
- Embedded agent chats: what you type into an agent a customer has placed on their site, and a random identifier stored in your browser so the conversation continues.
- Email from our customers: if a customer sends you email through Mattering, we keep a copy of the message and a record of unsubscribes, so that people who opt out are not emailed again. Some customers send outreach from their own mailbox through Mattering Sales. That customer is the sender and decides who to email; to stop their emails, reply "stop" or contact the sender. We keep a record of opt-outs and of addresses that bounced, so that those addresses are not emailed again.
When you visit our website
- Contact form: your name, email, business name and website, the reason for contacting us, and your message. We add these to our own sales records (we run them in Mattering) so we can reply and follow up.
- Server logs: our hosting provider records standard request information (IP address, page requested, user agent, time) for security and troubleshooting.
- Cookies: strictly necessary cookies always, analytics and attribution cookies only if you agree. See the Cookie notice.
Why we use it
- To provide the service: run your account, the apps, automations and agents, and show your organization's content to the people it shares it with. This is necessary to perform our contract with you or your organization.
- To keep it secure: authenticate you, detect misuse, and investigate incidents. This is in our legitimate interest and yours.
- To bill: apply plan limits, meter AI credits and automation runs, and take payment.
- To support and follow up: answer your requests and help new accounts get started. When you sign up, we create a record in our own sales system so our team can follow up about Mattering.
- To understand and improve our website: measure which pages and campaigns work, only with your consent where the law requires it.
- To meet legal obligations: for example tax records, and responding to lawful requests.
We do not sell personal data. We do not use customer content to train our own AI models. We do not use the content in your workspace for advertising.
How we use AI
Several Mattering features send content to an AI provider to produce an answer. Content is sent only when you, a teammate, an agent or an automation uses one of these features.
| Feature | What is sent | Providers |
|---|---|---|
| Agents: Matter and agents your organization builds, including the chat panel inside each app | Your messages, the agent's instructions and memories, and the app data, files, images, web pages, emails or call transcripts the agent reads to do the task | Anthropic by default; OpenAI or Google if your organization chooses those models |
| Agent voice on calls | The live speech of people on the call, and the agent's reply text to turn into speech | OpenAI. If you give the agent your own ElevenLabs or OpenAI key for its voice, the speech goes to that provider under your own account with them (see services you connect) |
| Comms: catch me up and draft a reply | The recent messages in the channel or thread | Anthropic |
| Productivity assistant | Your request and the tasks and project data it needs | Anthropic |
| Files used as knowledge | The text of files and folders you choose to add as knowledge, to summarize them and build a search index | OpenAI for the search index; the agent's model for summaries |
| Image and video generation | Your prompt and any reference images you provide | Google, OpenAI, Black Forest Labs, fal, Runway or Luma, depending on the model chosen |
| AI steps in automations, including SEO and research steps | The inputs you give the step, such as keywords, page content or drafts | Anthropic, and for search data DataForSEO |
Call transcription in Comms and in Productivity recordings runs on our own hosting and does not send audio to an AI provider.
We use these providers through their business APIs. Whether and how long each provider keeps the content, and whether it may use it to improve its models, is governed by that provider's API terms [To be confirmed per provider]. Where a provider offers a setting not to store a request, we use it where we have built it in (for example, Agents asks OpenAI not to store chat requests). If your organization connects its own AI account or key, that provider's terms with your organization apply.
AI output can be wrong. Summaries, drafts, extracted details and agent actions can be incomplete or incorrect, and can sound confident when they are not. Review AI output before you rely on it, and especially before sending it to someone, signing, paying or deciding something about a person. Agents can take actions such as sending email; your organization controls which tools an agent may use.
Information we receive from Google
Several Mattering apps let you connect a Google account. Each connection asks Google only for the permissions its feature needs, and Google lists them for you before you agree. This section explains what each connection reads, what we keep, where it can go, and how to stop it.
Mattering's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What each Google connection is for
| Where you connect it | Google permissions | What we do with them |
|---|---|---|
| Sales: your mailbox | Gmail read (gmail.readonly) and send (gmail.send) | Copy email between you and your contacts onto their records, and send the email you write and the outreach sequences you launch |
| Agents: an email account for an agent | Gmail read, label and archive (gmail.modify) and send (gmail.send) | Let the agent search, read, send, reply to, label and archive mail in the mailbox you give it |
| Calendar: your calendar | Google Calendar events (calendar.events) | Read when you are busy, so your booking pages do not offer those times, and add, change or cancel the events for your bookings |
| Files: Google Drive | Only Drive files you open or create with Mattering (drive.file) | Import a Google Docs, Sheets or Slides file you choose, and export a file to your Drive |
| Automations: Google Sheets | Sheets (spreadsheets) and read-only Drive (drive.readonly) | Find, read and write spreadsheets in the automations you build |
| Automations: Search Console, Business Profile and Analytics | Search Console (webmasters), Business Profile (business.manage), Analytics (analytics.readonly and analytics.edit) | Read reports and manage those accounts in the automations you build |
Google Calendar sync copies only the start and end of your other events and whether they show you as busy. It does not copy their titles, descriptions or attendees. Your Google access tokens are kept encrypted in our secret store, are used only to act as you for the feature you connected, and are not shown to other people in your organization.
Gmail in Mattering Sales
- What we read. With the read permission, we check the sender, recipients and subject of messages in your mailbox (not drafts, spam, trash or chats), going back as far as you choose when you connect, to find email between you and the contacts in your Sales workspace. We also use it to end an outreach sequence when a contact replies, to recognize replies asking us to stop and out-of-office replies, to notice bounced email, and to count how much mail the mailbox has sent recently so that outreach from a new mailbox starts slowly.
- What we keep. We copy only email that involves one of your contacts: its sender, recipients, subject, date, body (up to a size limit) and attachments (up to 10 per message and 25 MB in total). If your workspace has turned on automatic contact creation, an email from a new person who appears to be a real sender also creates a contact and is copied. Other messages are read only for the details above and are not kept. From a bounce notice we keep only the address that failed, on your do-not-email list. You can delete copied email yourself: one message from the contact's record, or everything copied from your mailbox in Sales settings (see Disconnecting and removing access).
- Who can see it. Copied email appears on the contact's record for the people in your Sales workspace. If you chose to log email privately when you connected, only you can see it.
- What we send. With the send permission, we send, from your mailbox, the email you write from a contact's record and the steps of outreach sequences that a person in your organization has launched. These messages appear in your Gmail Sent folder. We never send from any address other than the mailbox you connected.
- How replies are sorted. Replies to your outreach are sorted (a request to stop, an out-of-office reply, or a person replying) by fixed rules on our own servers, not by an AI model.
When Google data reaches an AI model
Google data reaches an AI provider only through features you or your organization use:
- Agents reading your Sales records. Email copied into Sales is part of your Sales workspace. When you or a teammate ask Matter or another agent to work with a contact, the agent can read the email on that contact's record (but not email someone else logged privately) and sends it to the agent's AI model to do the task: Anthropic by default, or OpenAI or Google if your organization chooses those models.
- AI assistants you connect. If you connect an AI assistant outside Mattering to your account, for example through our MCP server, it can read the same email when you ask it to, under that assistant's own terms.
- An agent's own mailbox. An agent with an email account sends the messages it opens to its AI model to do the task you gave it, and what it reads is kept in its conversation history.
- Automations. An automation your organization builds to start when a contact emails you receives the sender, the subject and the first part of the message (nothing for email logged privately), and passes them to the steps you set up, which can include an AI step. Data from Sheets, Search Console, Business Profile or Analytics reaches an AI model only if an automation or agent you set up sends it to one.
Our commitments for Google data
- We use Google user data only to provide and improve the features described above, which you can see and control in the apps.
- We transfer it to others only as needed to provide those features (for example, to the AI provider an agent uses, or to a service an automation you built sends it to), for security purposes such as investigating abuse, to comply with the law, or as part of a merger, acquisition or sale of assets after asking for your explicit consent.
- We do not use it for advertising, including retargeting and personalized or interest-based ads, and we do not sell it.
- We do not use it to develop, improve or train generalized AI or machine learning models, and we send it only to AI providers whose business API terms do not allow them to train their models on it.
- No one at Mattering reads it unless you give us permission for specific messages or files (for example, in a support request), it is needed for security purposes such as investigating abuse, it is needed to comply with the law, or it has been aggregated and anonymized for our internal operations.
Disconnecting and removing access
- Disconnect in Mattering. You can disconnect a mailbox in Sales settings, a calendar in Calendar's integrations, an agent's email account in the agent's settings, and any Google connection on the Automations Connectors page. Disconnecting stops Mattering from using that connection: a disconnected mailbox stops syncing and sending, and outreach sequences left with no mailbox to send from are paused.
- The stored token. When you disconnect, we destroy the token we stored for that connection and ask Google to revoke Mattering's access. One exception: Google ends all of Mattering's access to a Google account at once, not one connection at a time. So if the same Google account is still connected to Mattering somewhere else in the same way (for example, the same mailbox in another workspace), we destroy only the token for the connection you disconnected and leave the others working. Mattering's access then stays listed in your Google account until you disconnect the last one, or remove it yourself as below. If Google cannot be reached, we still destroy the token.
- Remove access at Google. You can remove Mattering's access at any time on your Google Account permissions page. That takes effect straight away, and every token Mattering holds for that access stops working.
- Data already copied. Email already copied into Sales stays on your contacts' records after you disconnect, unless you choose to delete it. When you disconnect a mailbox you can tick "Also delete the email copied from this mailbox", and in Sales settings you can delete all email synced from your mailbox at any time, connected or not. The person whose mailbox an email came from, or a workspace admin, can also delete a single email from the contact's record. Deleting removes our copy of the message, its attachments and its timeline entry, and the mailbox sync does not copy it again; your Gmail is not changed. If the same message is also in a teammate's connected mailbox, their copy stays with them. Deleting a contact (not archiving it) also deletes the email linked to it. Otherwise copied email is deleted when the organization is deleted, and email you logged privately is deleted when your account is deleted. When you disconnect a calendar, we delete the busy times we copied from it; your bookings stay. Files you imported from Drive stay in Files until someone deletes them.
Who receives personal data
We share personal data only in these cases:
- Service providers (subprocessors) that host, store, email, bill, carry calls or run AI for us. Each one is listed, with what it receives and why, on our Subprocessors page.
- Services you connect. When you connect another service or build an automation that sends data to one, that data goes where you told it to go, under that service's terms.
- Inside your organization. Content is visible to the people in your organization it is shared with, and to anyone you share a link or invite with.
- Content delivery. Our pages load fonts, icons and code libraries from public networks (Google Fonts, cdnjs, jsDelivr, code.jquery.com and cdn.datatables.net). These networks receive your IP address and browser details when your browser fetches the files.
- Legal reasons. If the law requires it, to protect people from harm, or to enforce our terms.
- A change of ownership. If Mattering is merged or sold, data would transfer under this policy.
How long we keep it
Here is how the product behaves today:
- Account and organization data is kept while the account or organization exists.
- Workspace content is kept until someone in the organization deletes it, or until the organization is deleted and we complete its removal (see below).
- Deleted files go to the trash for 30 days, where they can be restored. After that they are eligible for permanent removal, including their versions and any search index built from them.
- Audio sent for call transcription is deleted once it is transcribed, and within 24 hours at most.
- An agent's saved browser session data expires after 14 days.
- Contract signing links expire after 120 days. The signed contract and its audit trail are kept with the contract.
- Form responses, booking records and QR scan records are kept until the customer deletes them.
- Data pulled into the Analytics app is kept for 400 days by default, which the customer can change.
- Sign-in and security records do not yet have a fixed deletion period [To be confirmed: security log retention period].
- Billing records are kept as long as tax and accounting law requires.
An organization owner can delete the organization from its settings. Members lose access straight away, and the owner can still cancel for 30 days. After those 30 days we erase the organization and its content in every app. If you want confirmation that everything has been erased, send a request as described below.
Your choices and rights
Depending on where you live, you may have the right to:
- ask for a copy of the personal data we hold about you (access and portability);
- ask us to correct it;
- ask us to delete it;
- object to, or ask us to limit, some uses, including direct marketing;
- withdraw consent you gave, such as for analytics cookies, at any time;
- complain to your local data protection authority.
How to make a request
- Do it yourself: you can change your time zone in your settings, delete content you created, export some content from the apps directly (for example files, Comms messages, agents and automations), and use "Export my data" in your account settings to get a copy of your own data from every app. An organization owner can request an export of the whole organization.
- Everything else: use our contact form, choose Support, and start your message with Privacy request. Tell us what you want and the email address on your account. We may ask you to confirm that the request comes from you. We aim to respond within 30 days.
- Data a customer holds about you: if your request is about a form, contract, booking, call or other content a Mattering customer controls, please contact that organization. If you contact us instead, we will pass your request to them where we can.
- Deleting your account: use "Delete my account" in your account settings. You are signed out and removed from every organization, and your private content in every app is deleted; work you shared stays with your organization, credited to "Deleted user". If you are the only member of an organization, it is deleted with your account after the same 30 days, and you can cancel until then. You can also send a request as above.
We will not treat you differently for using any of these rights.
How we protect data
We take reasonable technical and organizational steps to protect personal data. In plain terms: traffic to Mattering is encrypted in transit; passwords and API keys are stored only as one-way hashes; connected-account credentials live in a separate secret store, and their use is logged; sign-in cookies cannot be read by page scripts; and access to customer data inside Mattering follows organization, workspace and sharing permissions. No system is perfectly secure. If we learn of a breach that affects your personal data, we will tell you and any regulator as the law requires. We do not currently hold security certifications, and we do not claim to.
International transfers
Mattering is operated from the United States [To be confirmed], and our providers may process data in the United States and other countries. Those countries may have different data protection laws from yours. Where the law requires it, we rely on recognized safeguards for these transfers, such as standard contractual clauses [To be confirmed: transfer mechanism and DPA availability].
Children
Mattering is a tool for work and is not directed to children. You must be at least [To be confirmed: 16] years old to create an account. We do not knowingly collect personal data from children under 13. If you believe a child has given us personal data, contact us and we will delete it.
Contact us
For questions about this policy or your data, use our contact form, choose Support, and start your message with Privacy request. [To be confirmed: postal address]
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. |