Where your data goes

The short version

• We keep the report, which quotes the numbers it explains. We do not keep the numbers you typed in, unless you ask us to show them on the shared link.
• You can call your client anything you like. We never need their real name.
• Claude, made by Anthropic, reads your numbers, notes and any screenshots to write the report, and the paragraph you ask it to rewrite. Words you type into the report yourself only go to Anthropic if you then ask for that paragraph to be rewritten. Anthropic does not train its models on what it reads, and deletes it after a limited period set by its terms.
• Signing in with Google and connecting your Google accounts are optional. If you connect them, matcha only reads from them, and nothing it gets from Google goes to our analytics.
• If you pay for a plan, Stripe takes the payment. Your card goes straight to Stripe, and Stripe never sees your clients or your reports.
• We do not sell data, and there are no ads.

What happens when you make a report

1. Your browser sends the form to our server over an encrypted connection.
2. Pasted numbers and CSV files are read in your browser. Screenshots go to Anthropic once, so Claude can read the numbers off them, and are dropped. You check what was read before anything is written.
3. When you press Make my report, our server passes the numbers, your notes and, if you set one for that client, its goal to Anthropic, and Claude sends the paragraphs back. Rewriting a paragraph, or answering a question on the report, sends that paragraph and your answer the same way.
4. We save the report with the client name, platform and period. If you turn on the numbers table in Share, we save the table too. Turn it off and we drop it again. Your notes, answers, screenshots and the rest of the form are dropped.
5. You get a link. The first time you want one on a browser we ask for your email address. After that the link comes straight away. Anyone who has it can read the report, so send it only to people who should see it. Links are random, search engines are told not to list them, and we never publish them anywhere.

What we keep

The written report

Yes. It is what your link opens, and it quotes the numbers it explains.

Client name, platform and period

Yes, as you typed them, because they head the report. A nickname is fine.

The numbers you typed in

No, unless you turn on “Show the numbers table on the link” in Share. Then we keep them so the page can show them as a table, and turning it off drops them again. Any figure the report quotes stays in its text either way.

Screenshots and CSV files

No. A CSV file is read in your browser and never sent to us. Screenshots go to Claude once, to read the numbers off them, and are then dropped. We never save them, and what we read goes into the list for you to check, under the same rule as numbers you type.

What happened this month

No. We pass your notes, and any answers you give to the questions on a report, to Claude to write it, and we never save them. The report may mention what they said. A voice note is turned into words on your own device, only in browsers that can do that, and the recording never leaves it.

Your email address

Only if you give it. We ask for it the first time you want a share link, and keep it so this browser is not asked again. If you join the waiting list on the home page, we keep that address too. Either way it never goes to our analytics or to Anthropic, and we remove it when you ask.

Notes you send us

Yes, if you use the Feedback tab or rate matcha after sharing a report. We keep what you type, the stars, and the page you were on, your screen size and your browser type so we can fix a problem. If you choose to say what you do and how you found us, we keep that too. An email address is optional and only used to reply. If you are signed in, the note is tied to your account. None of it goes to our analytics (which only learns that a note was sent) or to Anthropic, and we remove it when you ask. Please leave client names and numbers out of it.

Your IP address

No. We keep a scrambled version to count how many reports, screenshot reads and rewrites a visitor asks for, which is the fair use limit. If you sign in, we count by a scrambled version of your account id instead, so your usage follows you from one device to the next. Our analytics tool is set to throw the address away. If you sign in, Supabase's sign-in service records the address it came from, as a security measure.

A saved report stays until you ask us to delete it. On Pro you can delete your own reports from your report list; otherwise, email us the link and we will remove it. On Free your 20 newest links stay live, and an older one is archived: its link stops opening the report, but we keep the report. Moving to Pro brings back the links for reports in your account. Archiving is not deleting, so ask us if you want an archived report gone.

Signing in and connecting Google

You can use matcha without an account, and a share link still needs only an email address. If you sign in, matcha can remember your clients and which Google accounts belong to each one. Reports you write while signed in are saved against your account, so they show up in your report list.

When you sign in, reports you wrote before on the same browser move into your account too. Reports written on another browser stay where they are, even if they used the same email address, and a report already in someone’s account never moves. Links that were live stay live. On Pro and Partner, any archived links among them come back.

Sign-in uses your Google account, through Supabase. Google learns that you signed in to matcha and nothing else about how you use it.

Connecting Google gives matcha access to Google Analytics, Search Console and Google Ads. Access to Analytics and Search Console is read-only. Google Ads has no read-only permission, so Google’s screen asks for wider access there, but matcha only reads reports from it and never changes a campaign.

Your sign-in

Your email address, an account id, and the basic profile Google shares when you sign in: your name and photo.

Your Google connection

The key Google gives us so matcha can ask for your numbers, called a refresh token. It is encrypted in Supabase Vault and only our server can read it. We also keep the Google account's id (not its email address), the permissions you granted, and when the connection was made, changed and last used. The short-lived tokens used for each request stay in our server's memory for under an hour and are never saved.

Your clients

The client names you save, and for each one which Google Analytics property, Search Console site and Google Ads account is theirs, by Google's id and the name Google shows for it.

A client's goal

If you set one, the single outcome that counts for that client: calls, orders, leads, sales or followers, or a word or two of your own, up to 24 characters. It is kept with the client and removed when you clear it or remove the client. When you write a report for that client while signed in, the goal goes to Anthropic with the numbers, so the report can open with the right one, and with any “Is this good?” question you ask on that report. It does not go to our analytics.

Client logos and colors

On Pro and Partner, the logo and brand color you add to a client. The logo is a PNG or JPEG file in private storage at Supabase, shown only on that client's reports and to you. Reports you write for that client keep the color and point at the logo. Removing the client deletes the logo, and those reports then show no logo. If you move back to Free, reports already written keep their branding, new ones have none, and you can still remove the logo.

Numbers from Google

Matcha fetches them only when you press Pull from Google, for the client and period you pick. They go to your browser, where you check them like numbers you paste, and then follow the same rule as numbers you type in: they are dropped once the report is written unless you turn on “Show the numbers table on the link” in Share. Any figure the report quotes stays in its text.

We use data from Google only to write your reports and to show you which accounts you can pick. None of it goes to our analytics. We never use it for ads, never sell it, and never use it to train AI models. When a report is written, the numbers go to Claude the same way typed numbers do, and Anthropic does not train on them. Nobody at matcha reads your Google data unless you give us permission, it is needed for security, or the law requires it.

When you connect Google, our analytics records your matcha account id (never your email address) and how many of the three Google products you allowed. When you pull numbers, it records the report type, whether it was a month, quarter or year, which Google products answered, how many numbers came back and, if it failed, a short error code. Never the numbers or the client.

Matcha’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.

You can disconnect Google at any time. Matcha asks Google to cancel its access first, then deletes the token. Your client names stay, and the accounts picked for them are cleared. You can also remove matcha’s access yourself at myaccount.google.com/permissions. To delete your account, email us. Within 30 days we cancel matcha’s access at Google, then delete the account along with its Google connection, its clients and their logos.

If you pay for a plan

Paid plans need you to be signed in. Stripe runs the checkout and takes your name, email address, card and billing address. We give Stripe your matcha account id too, so its messages about your subscription reach the right account. Your card goes to Stripe directly and never passes through matcha.

We keep which plan you are on, whether the subscription is active, when the current month ends, and the ids Stripe gives your customer record and subscription, so we can match its messages to your account. We keep no card details and no invoices. Stripe holds your invoices, and you can read them on its billing page, where you can also cancel or change your card.

Our analytics records that you started a checkout, and when a paid plan starts or ends, against your matcha account id. Never your email address and nothing about your card.

If you ask us to delete your account, we cancel your subscription first. Stripe keeps its payment records for as long as the law requires it to.

Who else sees it

Five companies help run matcha. Each sees only what it needs to do its part, and all five are based in the United States. Stripe only sees anything if you pay for a plan.

Google is not one of them. If you sign in with Google or connect your Google accounts, Google is where the data comes from, and we send it nothing beyond your sign-in and matcha’s requests for your numbers.

Anthropic

Writes the report, rewrites a paragraph when you ask, and reads numbers off screenshots. Matcha uses their Claude model. When a report is written: the client name, platform, period, numbers and notes. When you rewrite a paragraph or answer a question on it: that paragraph and your answer. When you add screenshots: the screenshots. Anthropic does not train its models on this, and keeps it only for a limited period under its commercial terms before deleting it.

Vercel

Hosts the website and runs the server. Everything passes through it on the way to Anthropic and the database.

Supabase

The database, and file storage for client logos. Saved reports, the email address you give for a share link or the list, a random id for your browser, and a scrambled form of your IP address used for the fair use limit. If you sign in, also your account (and a scrambled form of its id, which counts your usage in place of your address and how often you pull numbers from Google), the clients you save, and your Google connection, whose key is stored encrypted. On Pro and Partner, the logo and brand color you add to a client, with the logo kept in private storage. If you pay, your plan and the ids that link it to Stripe. A report keeps its table of numbers only when you turn on "Show the numbers on the link". If you typed in a result figure, it is kept with them.

PostHog

Product analytics. Which pages are visited, including report links, and which buttons are clicked. Screen recordings with every form field and every report blanked out. How long each report took and what it cost, but never what it said. If you connect Google, your matcha account id (never your email address) and how many of the three Google products you allowed. When you pull numbers from Google, the report type, whether it was a month, quarter or year, which Google products answered, how many numbers came back and, if it failed, a short error code. Never the numbers or the client. If you pay for a plan, which plan, and when it starts or ends. It is set to discard IP addresses.

Stripe

Takes payment for the paid plans, sends receipts and runs the page where you cancel or change your card. Only if you pay: your name, email address, card details and billing address, which plan you are on, and your matcha account id so its messages reach the right account. Your card goes straight to Stripe and never passes through matcha. Stripe never sees your clients, their numbers or any report.

When your client opens the link

We count the visit so we know links are being read, which means our analytics sees the link itself. Your client does not need an account. The report is blanked out of our screen recordings the same way it is on your side, and the page title does not name the client.

Cookies

When you write a report we set a cookie called ledger_visitor. It holds a random id for your browser, so we know which reports it wrote and whether it has already given an email address. It holds nothing else, and our analytics never sees it.

PostHog stores an identifier in your browser so a second visit counts as the same visitor, and the site remembers whether you picked the light or dark theme. There are no advertising cookies.

If you sign in, Supabase sets cookies that keep you signed in, and a short-lived one that only lasts while Google sign-in finishes. If signing in moved earlier reports into your account, a cookie called matcha_claimed holds how many, for up to a week, so your report list can tell you once. It holds that number and nothing else, and is deleted as soon as the note shows.

When you press Connect Google, we set a cookie called matcha_google_oauth for 10 minutes. It checks that the answer coming back from Google belongs to the request you started, and it is deleted as soon as Google sends you back.

If your client asks for a DPA

Some agency contracts need a data processing agreement from every tool that handles client data. We have one ready. Email blue.bookhard@gmail.com and we will send it over.

Your rights

You can ask for a copy of what we hold about you, ask us to correct it or delete it, or object to how we use it. Email blue.bookhard@gmail.com and we will reply within 30 days. If you are unhappy with the answer you can complain to the data protection regulator where you live.

We use your data to run the tool you asked to use, and to understand how people use it so we can improve it. Your email address is used only for what you gave it for. To have it removed, email us.

Who runs matcha

Matcha is run by Blue Tyler Bookhard. Questions about this page go to blue.bookhard@gmail.com. If what we keep changes, this page changes first, and the date at the top moves. The rules for using the tool are in the terms.