Matcha ("we", "us", "the app") is a personal AI agent that performs tasks on your behalf, such as scheduling calendar events and contacting businesses, or people you name, by phone or email. This policy explains what data we collect, why, and how it's handled.
When you connect your Google Calendar, we access calendar data (events, availability) solely to perform tasks you ask us to do, such as adding an event you have confirmed to your calendar or checking your availability. Matcha does not edit or delete events already on your calendar. We also store account/profile information you provide directly (such as your name and contact preferences) and records of tasks the assistant performs on your behalf, so you can review outcomes and so we can diagnose failures.
When you connect Gmail, Matcha accesses your email only when you ask it to do something with your email: (1) send an email you asked us to send, to a business or to a person you name, only after you approve the exact message, and read the reply in the same thread; (2) find and read a specific message you ask about (for example, "what did the salon quote me?"), by searching your inbox by sender, subject or date; and (3) summarize the messages that arrived in your inbox over a period you choose (for example, "summarize today's emails"). For a summary, we use each message's sender, subject, date and Gmail's short preview, not the full message, and cover at most the 100 most recent messages in that period.
You can connect Outlook (a Microsoft account) instead of Google. Outlook Calendar is used in the same way as Google Calendar: only to add an event you confirmed and to check your availability. Outlook Mail is used in the same three ways as Gmail, only when you ask, and a summary uses each message's sender, subject, date and Outlook's short preview. Matcha uses one email account at a time, Gmail or Outlook.
We never scan, index or monitor your inbox in the background. Nothing in your inbox is read unless you asked for it.
Contacts: if you allow it, when you ask Matcha to call or text someone, it searches your phone's contacts for that name and reads their phone numbers. Only the number you choose is sent to Matcha. Your address book is not uploaded.
Calendar on your device: if you allow it, Matcha reads when you're busy in your phone's calendar (start and end times only, not titles or details) and stores those times on our servers to check your availability. When you confirm an event, Matcha adds it to your phone's calendar; its title, time and notes pass through our servers to do that.
Location: if you allow it, when you ask for something nearby, Matcha uses your device's location for that one request and sends it to our search provider (Google Places) to find results near you, or to a weather provider when you ask about the weather. It is held for a few minutes to run the request and is not stored in your history.
Your account: when you sign in with Google, Apple, an emailed code or a passkey, we store your email address and an identifier from that sign-in provider. Sign-in codes and invite emails are sent through our email delivery provider. If you join the waitlist, we store your email, your consent and the country of your app store or device.
Your profile: details you choose to give Matcha so it can act for you, such as your name, phone number, home area, preferred language and, if you verify it, the number Matcha calls from on your behalf.
Your requests and conversations: what you ask Matcha, its replies, the plans you approve and the outcome of each task, stored encrypted so you can review them in your history.
Voice: if you allow the microphone, dictation is turned into text by your phone's speech recognition. In a live voice conversation with Matcha, your audio is streamed through our servers to our AI model provider (OpenAI) to hold the conversation; the audio is not stored, and the text of the conversation is kept in your history.
Phone calls: when you ask Matcha to call a business or a person you name, the call is placed through our telephony provider (Twilio) and Matcha's AI voice speaks for you. Calls are recorded and transcribed. The recording and transcript are stored encrypted with that task, so you can see what was said and so we can investigate a failed or disputed call.
Notifications: if you allow notifications, we store your device's push token so we can tell you when a task needs you or has finished.
Diagnostics: if the app crashes or hits an error, it sends us the error details (such as the error message and the screen it happened on), and while you're signed in the app records which screens you open and how a task's status changes on screen, never what you type or say, so we can find and fix problems. We do not use third-party analytics or advertising SDKs, and we do not use an advertising identifier.
Feedback: messages you send us from the app, any screenshots you choose to attach to them, and any rating you give a task. Screenshots you attach to feedback are stored encrypted and deleted with your account. They are seen only by the Matcha team, not by the AI.
Photos and files you attach to a request: when you add a photo or PDF to a request, it is stored encrypted and kept with that conversation until you remove it or delete your account. A file you add but never send is deleted after 24 hours. To work on your request, Matcha's AI model provider (OpenAI) reads the file, and reads it again for any follow-up question about it, and Matcha keeps an encrypted record of what it shows, including any text, names, numbers and amounts in it. Photos may show people; Matcha is built not to identify anyone in them.
Products online: when you ask Matcha to find something to buy, it sends Shopify's catalog a search: words describing what you want, your country and its currency, and any price limit you gave, but not your name or contact details. Matcha keeps the products you were shown for 24 hours so you can open them again. Product photos load from Shopify's servers. Matcha can't buy anything for you: you buy on the store's own page.
Hotels and rental cars: when you search for a hotel or a rental car, Matcha sends what the search needs to Jinko, the travel company that sells them: the place and your dates, the number of guests and any children's ages (or for a car, the pick-up and drop-off places and times and the driver's age), any budget or rating you asked for, the currency, and your country, taken from your phone number. It keeps the offers you were shown for 24 hours. Hotel and car photos load from Jinko's and its suppliers' servers. When you ask Matcha to book one, it asks you for the details Jinko needs: each guest's name, or for a car the driver's name, title and date of birth, and a contact email and phone number. They are sent to Jinko only after you approve the booking, together with an identifier for your Matcha account that does not reveal who you are. You finish the booking and pay on Jinko's own page.
Matcha does not take payments today, so we hold no card or bank details.
Your data is used only to operate the features you use. We do not sell your data, and we do not use Google user data for advertising. Sensitive data (such as profile details and call transcripts, where applicable) is stored encrypted at rest.
Your data is not used to train AI models, by Matcha or by our AI model provider, OpenAI. That includes your conversations with Matcha, your voice conversations, the recordings and transcripts of calls Matcha makes for you, your email, your connected accounts, and the photos and files you attach to a request.
Email data, from Gmail or Outlook, is used only to complete the request you made: to answer your question, write the summary you asked for, or send and follow up on the email you asked us to send. We treat the content of your emails as information, never as instructions. Matcha will not call, email or book anything because an email told it to; acting on something in an email always needs a request from you.
To answer your request, the relevant email content (the message you asked about, or the senders, subjects and previews being summarized) is processed by our AI model provider, OpenAI, acting as our service provider. It is used only to produce your answer or summary, and is not used to train AI models.
Matcha's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We only request the Google Calendar and Gmail scopes needed to perform the actions you explicitly ask for: Calendar scopes to add an event you confirmed and check your availability, and the Gmail send (gmail.send) and read (gmail.readonly) scopes to send an email you asked us to send and read the reply, find and read a specific message you ask about, and summarize your recent inbox when you ask. We do not use Google user data to serve ads. We do not use it to develop, improve or train generalized AI or machine-learning models. We do not share it with third parties except as needed to provide the feature you requested: our email and calendar providers, and the AI model provider that writes your answer or summary. People at Matcha do not read your email unless you give explicit permission (for example, when you ask us for support), it is needed for security purposes such as investigating abuse, or the law requires it.
Matcha connects to Outlook through Microsoft Graph and asks only for the permissions those actions need: Calendars.ReadWrite for Outlook Calendar, Mail.ReadWrite and Mail.Send for Outlook Mail (an email you approve is saved as a draft in your mailbox and then sent, which needs write access; the same permission lets us find and read a message you ask about and the reply to an email we sent), User.Read to read your account's email address, and offline_access to keep the connection until you disconnect it. Calendar and email are connected separately, so connecting one never grants the other. Microsoft user data is handled under the same limits as Google user data above: it is not used to serve ads, not used to develop, improve or train generalized AI or machine-learning models, not sold, shared only as needed to provide the feature you requested, and not read by people at Matcha unless you give explicit permission, it is needed for security purposes, or the law requires it.
Your data is encrypted in transit and at rest. The personal content behind Matcha (your conversations and the photos and files you attach to them, call recordings and transcripts, your profile, emails Matcha reads or drafts for you, and the access to the accounts you connect) is additionally encrypted with keys that belong only to your account, and those keys are protected by Amazon Web Services' key management service. Access to your data within Matcha is limited to what's needed to run and support the service. When Matcha uses AI to handle a request, it sends only the information that request needs.
Before Matcha sends an email for you, the draft you're asked to approve is stored encrypted with that task, and deleted once the email is sent. A draft that's never sent is deleted with your account.
When Matcha reads a specific message for you, an encrypted copy is kept for 24 hours so you can open the full email from the task's receipt, then deleted. A summary keeps no copy of your emails; we record only how many messages it covered. The answers and summaries Matcha gives you are stored encrypted in your conversation history until you delete your account.
Call recordings and transcripts, your conversation history, your profile and your task records are kept until you delete your account. Device location is held only for the request that used it.
The traveller details for a hotel or car booking are stored encrypted with that task until Matcha hands the booking to Jinko, and are not kept after that. A booking you haven't approved within 24 hours can no longer be sent, and its details are deleted when you cancel it or 30 days after the task's last activity. If Matcha got you to Jinko's checkout page, it keeps a record of what was booked (the hotel or car, the dates, the price and terms, and Jinko's trip reference) with that task until you delete your account. Any other booking's record is deleted 30 days after the task's last activity.
Diagnostic records about your tasks are also kept until you delete your account. Database backups are kept for 7 days, then deleted automatically.
OpenAI does not keep the content of Matcha's requests after responding. It may keep logs for up to 30 days to detect abuse, then deletes them.
When you delete your account, we delete your data within 30 days. We also destroy your account's encryption keys, so any copy still in a backup can no longer be read. See Delete your account for what is deleted and what is kept.
You can disconnect your Google Calendar, Gmail, Outlook Calendar or Outlook Mail at any time from within the app. We then delete the access we held for it. For Google, we also withdraw Matcha's permission at Google once neither Google Calendar nor Gmail is still connected for that Google account. Microsoft doesn't let an app withdraw its own permission on a personal account, so to remove Matcha from your Microsoft account entirely, use account.live.com/consent/Manage. You can delete your account and its data at any time: see Delete your account.
We use these service providers strictly to operate the service, under contractual confidentiality obligations: Amazon Web Services (hosting, storage and encryption keys), OpenAI (the AI model behind Matcha's replies, voice and calls), Twilio (phone calls), Google Places (searching for businesses), Shopify (searching online stores), an email delivery provider (sign-in codes and invites), Apple and Google (push notifications), a weather data provider, and Google or Microsoft for the calendar and email accounts you connect. When you ask Matcha to call or email a business or a person, it shares what that request needs with them on your behalf. When you search for or book a hotel or rental car, Matcha shares what that request needs with Jinko, the travel company that sells it, as described above. We do not sell personal data.
Matcha is operated from Canada. Your data is stored and processed in the United States by our service providers, including Amazon Web Services and OpenAI. If you live outside the United States, including in Canada, the UK or Australia, your data is transferred there, and while it is there it may be accessible to courts, law enforcement and national security authorities in the United States under US law. We protect it with encryption in transit and at rest, keys that belong to your account, and contracts with our service providers that require them to safeguard it.
Questions about this policy or your data: support@matchaapp.ai