Effective date: September 7, 2026 Last updated: September 7, 2026
1. Overview
Matcha Productivity ("matcha.," "we," "us") builds a student planning app. This policy explains what we collect, why, who we share it with, and what control you have.
Two commitments up front, because they matter most:
- We do not sell your personal information, and we do not use it for targeted advertising.
- We do not use your content to train our own models, and we do not sell it. Your content is sent to third-party inference providers to generate plans and explanations — see Section 5, which explains exactly which providers and what commitments are and are not yet in place.
This policy covers the matcha. app, trymatcha.org, and related services (the "Service").
2. Age requirements
The Service is for students aged 13 and older. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has given us information, contact privacy@trymatcha.org and we will delete it.
If you are under 18, you need a parent or guardian's permission to use the Service. Parents and guardians can request access to, correction of, or deletion of their child's information — see Section 11.
3. What we collect
3.1 Information you give us
| Category | Examples |
|---|---|
| Account | Name, email address, password (hashed), school, grade level, time zone |
| Profile and goals | Courses, activities, sports, goals you set, study preferences, target colleges |
| Content you create | Tasks, notes, questions you ask the AI, homework photos and documents you upload |
| Communications | Support messages, feedback, bug reports |
3.2 Information from services you connect
Only after you explicitly authorize each connection, and only within the scopes we request:
| Connected Service | What we access |
|---|---|
| Google Calendar | Your primary calendar's events for a window around today — title, time, and whether the event is all-day. Read only. We request `calendar.events.readonly`, which cannot create, change, or delete anything in your calendar. (See Section 6 for a not-yet-enabled feature that would widen this to answering invitations.) |
| Microsoft 365 (Outlook Calendar, Teams assignments) | Calendar events and, where you enable it, Teams assignment titles and due dates |
| StudentVUE | Your assignments, courses, and grades from your district's Synergy portal |
| Canvas | Your active courses, their assignments and due dates, and your course grades, read from your school's Canvas site. You create an access token in Canvas and paste it into matcha; we store it encrypted. Read only. We never create, change, or delete anything in Canvas. |
| Edlink | Courses, assignments, and roster information your school makes available through Edlink |
We do not request access to your files or your contacts on any provider, and we have no Google Drive or Outlook Mail integration.
Mail and calendar replies are built but switched off. The Service now contains code for two features that are not enabled for anyone: reading your Gmail inbox to help you draft replies, and replying to Google Calendar invitations. While they are off, no Gmail scope is requested, no Gmail API call is made, and your calendar access stays read-only. We will update this policy, and Google will have reviewed and approved the additional permissions, before either is turned on. Section 6 describes what they would do.
You choose which of these to connect, and you can disconnect any of them at any time. Disconnecting one does not disable the rest of the Service. What disconnecting removes depends on the service. Disconnecting Google Calendar revokes our access at Google and deletes the calendar events we synced from it. Disconnecting StudentVUE or Canvas deletes the stored credential for that service, so nothing further is pulled from it — but the assignments and grades already synced stay in your planner until you close your account, because they have become part of the plan built around them. Section 11 explains how to close your account, which deletes them. Disconnecting Edlink deletes the stored connection, so nothing further is pulled from it.
3.3 Information collected automatically
- Device type, operating system, app version, language
- Log and diagnostic data: IP address, timestamps, crash reports, error traces
- Usage: features opened, plans accepted or rejected, notification interactions, focus timer sessions
- Push notification tokens
We do not use third-party advertising SDKs or cross-app tracking, and we do not build advertising profiles.
3.4 What we do not collect
We do not collect biometric identifiers, precise geolocation, payment card numbers (a payment processor would handle those directly if we introduce paid plans), or government identification numbers.
We also do not collect the contents of your email, your cloud files, your messages on chat platforms, or any video or audio recording. The Service has no such integrations.
4. How we use it
- Run the core product. Sync your assignments and events, build your daily plan, detect conflicts, and send notifications and briefs.
- Generate study material. Produce summaries, flashcards, quizzes, review sheets, and explanations tuned to your courses.
- Answer your questions. Route homework questions to our AI agents.
- Maintain continuity. Keep long-term memory of your courses, goals, and patterns so the Service does not start from zero each session.
- Keep people safe. Detect abuse, investigate reports, and enforce our Terms.
- Support and fix. Respond to your messages, debug problems, and monitor reliability.
- Improve the Service. Analyze aggregated and de-identified usage patterns. We do not need your individual content to do this.
- Comply with law. Meet legal obligations and respond to valid legal process.
We do not use your information for advertising, and we do not sell it or share it for cross-context behavioral advertising.
5. AI processing
Your content is processed by AI models to produce plans, explanations, and study material.
What reaches a model. The text you type, images you upload for extraction, your saved preferences, and — so the planner does not schedule over something you already have on — the titles and times of events on your calendar, including events synced from Google Calendar.
Providers. Your prompts and the schedule context around them are sent to third-party inference providers: NVIDIA, OpenRouter — which may route a request onward to a backing provider such as DeepInfra or CoreWeave — and SiliconFlow. Which provider handles a request depends on the model selected for that feature.
Human review. We do not routinely read your content. A member of our team may access specific content when you ask for support, when a safety report requires investigation, or when required by law. Access is limited and logged.
Automated decisions. The Service makes automated suggestions — what to work on, when to study, when to rest. These are recommendations only. They do not have legal or similarly significant effects, and you can ignore, override, or edit any of them.
Prompt injection. The event titles and assignment names we sync are written by other people — anyone who can send you a calendar invitation controls the text we read. That text may try to manipulate our AI agents. We escape it before a model sees it and we scope every action to your own records, but you should treat any surprising instruction or request in a matcha. output with suspicion and report it.
6. Google and Microsoft user data
Limited Use. 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.
Specifically, the only Google data we receive is Google Calendar event data, obtained through the read-only `calendar.events.readonly` scope. We use it only to build and display your schedule and to plan study time around your existing commitments. We do not transfer it to third parties except as necessary to provide those features (see Section 5 on AI processing), for security purposes, or to comply with law; we do not use it for advertising; and we do not allow humans to read it except with your explicit consent for support, for security investigations, or where required by law.
We request no Gmail scope and no Google Drive scope today.
What changes if the mail and invitation-reply features are enabled. This is stated in advance so that it is not a surprise, and because the code is already in the Service even though it is switched off:
- Replying to invitations would widen the calendar scope from `calendar.events.readonly` to `calendar.events`, which can write. The only write it performs is changing your own attendee response on an invitation you were sent — accept, decline, or tentative. It cannot create, delete, or edit anyone's events.
- Mail would request `gmail.readonly` and `gmail.send`. We would read your inbox to show it to you, and read a small number of your recent sent messages to measure how you write — length, greeting, sign-off — so a draft sounds like you. The message you are replying to, and short extracts of your own recent sent messages, would be sent to the AI providers named in Section 5 to generate that draft. Those extracts are truncated and are not stored by us. Nothing is ever sent from your account without you reading the draft and pressing Send yourself; matcha never sends mail on its own.
- A message someone else sent you contains their words, and we would be processing those words on your behalf in order to help you reply. We do not use anyone's message content to train models, and our providers are bound by the terms in Section 5.
We request no Google Drive scope in any configuration.
The same commitments apply to data we obtain through Microsoft Graph for Outlook Calendar and Teams assignments. We request no Outlook Mail scope.
7. Student data commitments
The Service is offered directly to students, not sold to schools. Even so, we voluntarily commit to the standards that state student-privacy laws set for K-12 services, including California's SOPIPA, Illinois' SOPPA, and New York Education Law § 2-d:
- We do not sell student data.
- We do not use student data for targeted advertising, on or off the Service.
- We do not build a profile of a student for any purpose other than providing the Service.
- We delete student data on request, subject to legal retention requirements.
- We require our service providers to make the same commitments.
FERPA. FERPA governs schools, not services students sign up for on their own. When you connect StudentVUE or Edlink with your own credentials, you are sharing your own education records with us by choice; we are not acting as a school official. If we later enter a district agreement, we will operate as a "school official" under the direct-control exception and update this policy.
8. Who we share it with
Service providers, under contract, only to run the Service:
| Provider | Purpose |
|---|---|
| Supabase | Database, authentication, file storage, Edge Functions |
| Vercel | Application hosting |
| NVIDIA, OpenRouter, SiliconFlow | AI inference — see Section 5 |
Legal and safety. We may disclose information to comply with valid legal process, to enforce our Terms, or to protect the rights, property, or safety of any person. Where a child's safety is at risk, we may report to law enforcement or NCMEC.
Business transfers. If we are acquired or merge, information may transfer to the successor, which will remain bound by commitments at least as protective as this policy. We will notify you before your information becomes subject to a materially different policy.
We do not share your information with data brokers, advertisers, or analytics companies that use it for their own purposes.
9. Retention
| Data | Retention |
|---|---|
| Account and profile | While your account is active |
| Synced calendar events (Google Calendar) | Until you disconnect Google Calendar, which deletes them |
| Synced coursework (StudentVUE, Canvas) | Until you close your account. Disconnecting deletes the stored credential and stops new coursework arriving; assignments and grades already synced remain |
| Content you create (tasks, notes, preferences) | Until you delete it or close your account |
| Logs and diagnostics | 90 days |
| Deleted account | Purged on request; backups within 90 days |
We may retain limited records longer where law requires it or where a safety investigation or legal claim is pending.
10. Security
We protect information with encryption in transit (TLS) and at rest, row-level access controls so users can only reach their own records, encrypted storage of third-party access tokens, least-privilege access for our team, and audit logging of administrative access.
No system is perfectly secure. If a breach affects your personal information, we will notify you and applicable regulators as required by law, including under Washington's data breach notification statute and equivalent laws.
Please use a strong, unique password and enable multi-factor authentication if available.
11. Your choices and rights
You can, from within the app or by contacting us:
- Access the information we hold about you
- Export your data in a portable format
- Correct inaccurate information
- Delete specific content or your entire account
- Disconnect any Connected Service, which stops future syncing
- Control notifications, including quiet hours and channels
Parents and guardians of users under 18 may request access to, correction of, or deletion of their child's information by writing to privacy@trymatcha.org. We will verify the relationship before acting, and we will consider the minor's own safety and interests where a request appears to conflict with them.
Residents of California, Colorado, Connecticut, Virginia, Washington, and other states with comprehensive privacy laws have rights to know, access, correct, delete, and opt out of sale or targeted advertising. We do not sell personal information or use it for targeted advertising, so there is nothing to opt out of, but the other rights are available above at no charge. You may also appeal a denied request by writing to privacy@trymatcha.org. We do not discriminate against anyone for exercising these rights.
To exercise any right, contact privacy@trymatcha.org. We respond within 45 days, extendable once where the law permits.
12. Cookies and similar technologies
Our website uses cookies that are strictly necessary for authentication and security. We also use first-party analytics, which measures page views and a small number of product events without setting a cookie and without identifying you. We do not use advertising cookies or third-party trackers. You can control cookies through your browser settings, though disabling necessary cookies will break sign-in.
13. International users
The Service is operated from the United States, and your information is stored and processed there. If you use it from outside the US, you consent to that transfer. We do not currently offer the Service in the European Economic Area or the United Kingdom.
14. Changes to this policy
We may update this policy. For material changes we will give notice in the app or by email at least 14 days before the change takes effect and update the "Last updated" date. If a change would newly permit us to use previously collected personal information in a materially different way, we will obtain your consent first.
15. Contact
Privacy questions: privacy@trymatcha.org Safety reports: safety@trymatcha.org Support: support@trymatcha.org