Privacy Policy

1. Introduction

Matter, Inc. (“Matter,” “we,” “us,” or “our”) is committed to protecting your privacy. This Privacy Policy describes how we collect, use, share, and protect your personal information when you use the Matter mobile application (“App”), website (“Website”), and related services (collectively, “Services”).

This policy is designed to comply with the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA) as amended by the CPRA, and other applicable data protection laws.

By using the Services, you acknowledge that you have read and understood this Privacy Policy.

2. Data We Collect

2.1 Account Information

• Email address
• Name (first and last)
• Role (athlete or coach)
• Age and biological sex (provided during onboarding, used for baseline calibration)
• Authentication credentials (managed via Apple Sign-In or Supabase Auth)

2.2 Health and Biometric Data

We collect health data that you explicitly authorize through Apple HealthKit permissions or third-party wearable connections:

• Heart rate data: Resting heart rate (RHR), heart rate variability (HRV/RMSSD/SDNN), continuous heart rate samples
• Sleep data: Total sleep duration, sleep stages (deep, REM, core/light, awake), sleep onset and wake times, sleep consistency metrics
• Activity data: Steps, active energy burned (calories), workout duration, workout type and sport
• Workout data: Planned workouts, completed workouts, exercise heart rate, RPE (rate of perceived exertion)
• Recovery metrics: Recovery scores computed from the above biometrics

2.3 Wearable Device Data

If you connect a third-party wearable, we receive data from that provider:

• Apple Watch (via Apple HealthKit): All health categories you authorize in the Apple Health permissions dialog
• WHOOP: HRV, resting heart rate, recovery score, strain, sleep stages, and sleep performance via WHOOP API (OAuth 2.0)
• Polar: Heart rate, HRV, nightly recharge, sleep stages, exercise sessions, and daily activity via Polar AccessLink API (OAuth 2.0)

We only access data categories you explicitly authorize. You can revoke access at any time through your device settings or the wearable provider's app.

2.4 User-Generated Content

• Wellness survey responses (mood, energy, soreness, stress ratings)
• AI chat messages and conversation history
• Coach notes and messages to athletes
• Activity status updates
• Onboarding preferences (goals, challenges, sport preferences)

2.5 Usage and Device Data

• Device type and operating system version
• App version
• Crash reports and diagnostic logs (anonymized)
• Feature usage patterns (aggregated)
• Timezone and locale (for score computation accuracy)

2.6 Coach-Athlete Relationship Data

• Team membership and invite codes
• Data sharing preferences (which metrics an athlete shares with their coach)
• Workout assignments and completion status
• Compliance and adherence records

2.7 Google Account Data (Optional)

If you choose to connect Gmail or Google Calendar, Matter receives the data described in section 4.8: the address of the connected Google account; for a coach who turned on inbox reading, email metadata; and for a team calendar, event titles and times.

3. How We Use Your Data

3.1 Core Service Delivery

• Computing daily readiness, recovery, strain, sleep, and stress scores
• Building personal baselines from your biometric history (7–14 days of data)
• Generating AI-powered daily insights and recommendations
• Creating AI-generated workouts adapted to your current readiness
• Providing AI chat responses that reference your health context
• Displaying trend charts and historical analysis

3.2 Coach Features

• Presenting shared athlete metrics on the coach dashboard
• Generating team intelligence summaries and morning briefings
• Enabling workout assignment and compliance tracking
• Producing weekly team performance reports

3.3 Personalization

• Calibrating scores to your individual baselines (not population averages)
• Adjusting AI recommendations based on health conditions you disclose
• Remembering AI chat context across conversations (ChatMemoryStore)
• Applying coach-configured metric weightings to readiness calculations

3.4 Service Improvement

• Analyzing aggregated, de-identified usage patterns to improve features
• Monitoring AI output quality and accuracy
• Debugging technical issues using anonymized diagnostic data

3.5 Communication

• Sending transactional emails (account verification, password reset)
• Delivering in-app notifications (readiness alerts, coach messages, workout reminders)
• Responding to support requests

4. AI-Powered Insights & Third-Party Data Sharing

4.1 How AI Uses Your Data

Matter uses three third-party AI providers, and only after you explicitly grant consent in the iOS app at Settings → Privacy → AI Insights. You can revoke consent at any time, which immediately stops all AI calls and clears any AI-generated content cached on your device.

Google LLC (Gemini, accessed via Firebase AI and Supabase Edge Functions) powers:

• Daily health insights and recommendations
• AI chat assistant responses (athlete and coach)
• Workout generation and adaptation
• Photo or whiteboard scans
• Class post-session summaries
• Coach morning briefings and draft message generation
• Supporting steps of the coach assistant, such as suggested follow-up questions. For coaches who turned on Gmail inbox reading, this can include the assistant's answer about their email (see section 4.8)

OpenAI, LLC (GPT models, accessed via Supabase Edge Functions) powers:

• Athlete and coach readiness narratives
• Team intelligence reports
• Document and journal summaries

Anthropic, PBC (Claude models, accessed via Supabase Edge Functions) powers:

• The coach AI assistant (chat, workout and program drafting, and draft messages)
• For coaches who turned on Gmail inbox reading, answers to the coach's own questions about their email (see section 4.8)

When either AI provider processes your data, a compressed summary of your relevant health context is sent as part of the prompt. The summary may include: recent readiness/recovery/strain/sleep scores, personal baselines and trends, workout history and exercise logs, health conditions and medications you've entered, journal entries and behavioral signals, and demographics (age, biological sex, sport, training level). Raw biometric time-series data and unaggregated HealthKit waveforms are never sent to any provider.

Each request is per-user and is not used by any provider to train their AI models. Each provider is contractually obligated under their published privacy policies to provide protection equal to ours:

• Google: https://policies.google.com/privacy
• OpenAI: https://openai.com/policies/privacy-policy
• Anthropic: https://www.anthropic.com/legal/privacy

4.2 Third-Party AI Processors

Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States, acts as a data processor for AI inference through the Google Gemini API (accessed via Firebase AI and Supabase Edge Functions). Google processes data under the Gemini API Terms of Service and the Google Privacy Policy.

OpenAI, LLC, 3180 18th Street, San Francisco, CA 94110, United States, acts as a data processor for AI inference through the OpenAI API (accessed via Supabase Edge Functions). OpenAI processes data under the OpenAI Privacy Policy.

Anthropic, PBC, 548 Market Street, PMB 90375, San Francisco, CA 94104, United States, acts as a data processor for AI inference through the Anthropic API (accessed via Supabase Edge Functions). Anthropic processes data under its Commercial Terms of Service and the Anthropic Privacy Policy.

Data fields sent to AI providers as part of prompt construction:

• Health metrics (HRV, resting heart rate, sleep, readiness)
• Workout history and exercise logs
• Health conditions and medications you've entered
• Journal and behavioral trend data
• Demographics (age, biological sex, sport, training level)

What is NOT sent to any AI provider:

• Name, email address, or phone number
• Home address or precise GPS location
• Raw HealthKit sample IDs or continuous sensor time-series

All data is transmitted over TLS 1.2+.

4.3 Data Sent to AI Providers (Detailed Breakdown)

4.4 Retention and Model Training

• Neither Google nor OpenAI retains data from API requests beyond each individual request — your health context is not stored by either provider after the response is returned
• AI prompts and responses are cached locally on your device (UserDefaults LRU cache) and in-memory for performance
• We do not use your personal health data to train or fine-tune AI foundation models
• Per Google's Gemini API terms, your data is not used to train or improve Google's general-purpose models; per OpenAI's API terms, your data is not used to train OpenAI models
• Per Anthropic's commercial API terms, inputs and outputs sent through the Anthropic API are not used to train Anthropic's models by default. Anthropic keeps API inputs and outputs only for a limited period (currently up to 30 days) for trust and safety purposes, then deletes them, unless a longer period is required by law or by its usage policies

4.5 Equal Protection

Google's, OpenAI's, and Anthropic's protection of your data is at least equal to the protections we provide under this Privacy Policy.

4.6 Consent and Revocation

Before any health data is sent to Google, OpenAI, or Anthropic for AI processing:

• New users see a dedicated onboarding consent screen that names Google LLC (Gemini) and OpenAI, LLC and lists the exact data fields above before any AI feature activates
• Existing users affected by material changes to AI data sharing see a re-consent sheet on next app launch
• Revoking consent: go to Settings → Privacy → AI Insights and toggle off AI features. This immediately stops all AI calls to both providers and clears cached AI content on your device

4.7 Your AI Data Rights

• Export: Settings → Privacy → Download My Data provides a copy of your health data and AI interaction history
• Deletion: Settings → Account → Delete Account permanently removes your data from our systems; Google retains no data per-request
• GDPR / UK GDPR: EEA and UK residents retain all rights under applicable law including access, rectification, erasure, restriction, portability, and the right to object. Contact privacy@matterperformance.com to exercise these rights

4.8 Google User Data (Gmail and Google Calendar) and Limited Use

Matter's use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Connecting a Google account to Matter is optional. Matter asks for each permission in its own step, only when you choose to connect that feature. This section says what Matter accesses in a Google account, why, what it stores, who receives it, how long it is kept, and how to remove it.

Gmail: sending email

A coach can connect their own Gmail account so that the email they send from Matter goes out from their own address and replies come back to them. Athletes never connect Gmail.

• What Matter accesses. When a coach connects Gmail, Matter asks only for permission to send email (gmail.send) and to see the address of the account that was connected. Matter uses it to send the emails that coach writes or approves in Matter, from the coach's own address. With this permission Matter cannot read, list, change or delete any email in the coach's mailbox.
• What Matter stores. The connected Gmail address, Google's identifier for that account, and Google's access tokens (the refresh token is stored encrypted). Matter stores nothing from the mailbox. An email a coach drafts and sends with the Matter assistant is kept in that coach's message history in Matter, as it is when the email is sent from Matter's own address, together with the identifier Google returns for the sent message.

Gmail: reading the inbox (optional, by request)

A coach can separately ask Matter to read their inbox. This is a second permission (gmail.modify) that the coach grants in its own step, and it is available only to coaches Matter has enabled it for. When a coach asks, Matter records the request (the coach, their team and the Google address) and sends it to Matter's administrator to approve. The rest of this subsection applies only to coaches who have turned inbox reading on.

• What Matter reads. Matter reads the connected coach's mailbox and shows it only to that coach. By default Matter shows only mail to or from the athletes, parents, and staff on the coach's team. The coach can switch to all mail. Matter sends a reply, archives a thread, or marks it read only when the coach asks it to. Matter does not delete email.
• What Matter stores. Message metadata only: Gmail's identifiers for the thread and its latest message, the sender, the addresses on the thread, the subject, Gmail's short snippet (up to 300 characters), the date, Gmail labels, whether it is unread, and which athlete the thread matches or the coach linked it to. Matter also stores a marker of where the last sync stopped. Message bodies and attachments are fetched from Gmail when the coach opens a thread, downloads an attachment, or asks the assistant about the thread, and are not stored in Matter's database.
• Reply drafts. A reply the Matter assistant drafts is stored until the coach sends or dismisses it. Its text is cleared when it is sent.
• AI use. When the coach asks the Matter assistant about their email (for example, to summarize messages from parents or to draft a reply), the relevant email content is sent to Matter's AI providers only to answer that request: Anthropic, which runs the coach assistant, and Google's Gemini API, which Matter uses for supporting steps such as suggesting follow-up questions (see section 4.2). The assistant's answer, which may summarize an email, stays in that coach's chat history in Matter, visible only to that coach, until the conversation or the account is deleted. Matter keeps Gmail content out of its AI logs, feedback records, and evaluation data. With a send-only connection there is no mailbox content to send to an AI provider.

Google Calendar

• A coach's team calendar. A coach can connect a Google Calendar for their team (calendar.readonly and calendar.events). Matter reads the list of the coach's calendars and, on the calendars selected for sync (the primary calendar to start with; the coach can change the selection), the events in the next 30 days. From each event Matter keeps only the title, the start and end time, the time zone and whether it lasts all day. Matter does not keep attendees, descriptions, locations or attachments. The events are shown on the team's calendar in Matter, next to training sessions, to the coaches on that team, so they can plan around games, travel and classes. When a coach exports sessions, Matter writes those sessions as new events to the primary calendar of the connected Google account.
• An athlete's calendar. An athlete can connect their own Google Calendar (calendar.events, and the address of the account) so that Matter adds their assigned workouts to their main calendar and keeps them up to date. Matter marks each event it creates and afterwards lists, changes or removes only those events. It does not read the athlete's other events.
• What Matter stores. For a team calendar: the connected address, Google's access tokens, the list of calendars and which are selected, and the event titles and times described above, which are replaced each time the calendar syncs. The tokens cannot be read by coaches or athletes through Matter. For an athlete's calendar: the connected address and Google's access tokens (the refresh token is stored encrypted).
• AI use. When a coach asks the Matter assistant to sync Google Calendar, the assistant's AI provider is given the names of the calendars that were synced and how many events were found. Event titles and times are not sent to an AI provider.

Google Meet and a Doc the coach picks

• Meet spaces. When a coach connects Google Calendar, Matter also asks for permission to create a Meet space the coach owns (meetings.space.created) and to read Meet spaces that account can already open (meetings.space.readonly). Matter does not request drive.meet.readonly. A coach can draft a meeting for an athlete, a group, or the calendar, and from the coach assistant. Matter creates the Meet link only after the coach approves that draft. Matter stores the title, the time, who was invited, and the Meet link.
• Transcripts and notes. After a meeting, Matter can show the transcript and notes Google makes available for that space, on the meeting and on the athlete timeline. A summary sentence is shown as a finding only when it links to a transcript line. If the coach's Google Workspace plan cannot transcribe meetings, Matter says so and does not invent a transcript.
• A Doc the coach picks. Import notes uses the Google file picker and drive.file. That permission covers a Doc the coach picks in the picker, and files Matter itself creates. It does not let Matter browse or read the coach's Drive. Matter does not request drive, drive.readonly, or drive.meet.readonly.
• Weekly coach video. A coach can record or upload a video, write a message, and set a weekly time for all athletes or one group. The video is stored with the same upload path as Film Room upload. After the coach previews and approves, the video stays queued until the weekly send runs. It is not marked sent at approval.
• What is removed. Disconnecting Google removes Matter's copy of Meet links, transcripts, imported Doc text, and the tokens used to create them.

Who receives Google user data

• Supabase (database and server functions) stores and processes it for Matter.
• Vercel hosts the Matter web application. Its servers handle the connection with Google and the Google Calendar sync; the data is stored in Supabase, not on Vercel.
• Anthropic and Google (Gemini API) receive email content only for a coach who turned on inbox reading and asked the assistant about their email, as described above.
• Resend delivers Matter's own notification emails. The only Google detail these can contain is a connected email address, for example in the request a coach sends to turn on inbox reading.
• Sentry receives technical error reports when a connection or sync fails. Matter does not send it email content or calendar event details.

No other app, service or person receives Google user data from Matter.

How Matter limits its use of Google user data

• Matter uses Google user data only to provide and improve the features described in this section, which you can see and control in Matter.
• Matter does not sell Google user data, and does not transfer it to advertising platforms, data brokers or information resellers.
• Matter does not use Google user data for advertising, including retargeting, personalized or interest-based advertising, or to determine credit-worthiness or for lending.
• Matter does not use Google user data to create, train or improve generalized artificial intelligence or machine learning models, and does not allow its AI providers to (see section 4.4).
• Matter transfers Google user data only to the providers listed above, as needed to provide these features; for security purposes (for example, investigating abuse); to comply with applicable law; or as part of a merger, acquisition or sale of assets, and then only after obtaining your explicit prior consent.
• People at Matter do not read Google user data, except with your consent to view specific messages or data (for example, when you ask us for help with them), when necessary for security purposes (for example, investigating a bug or abuse), to comply with applicable law, or when the data has been aggregated and anonymized and is used for internal operations.

How long Matter keeps Google user data, and how to delete it

• How long. Connection details and tokens are kept until you disconnect or delete your account. For inbox reading, each time Matter syncs the mailbox (about hourly while connected) it removes message metadata older than 90 days and unsent reply drafts older than 14 days. Team calendar event titles and times are replaced at each sync.
• Disconnecting Gmail. A coach disconnects each Google account in Settings → Integrations. Matter asks Google to withdraw its access and deletes the stored tokens and, for inbox reading, that account's message metadata, reply drafts and sync marker. If the same Google account is also connected to Matter for something else, such as Google Calendar, Matter removes Gmail and its stored data and leaves the other connection working; disconnect that as well, or remove Matter at myaccount.google.com/permissions, to withdraw all access.
• Disconnecting Google Calendar. A coach disconnects the team calendar in Settings → Integrations; an athlete disconnects theirs on the Connections page. Matter asks Google to withdraw its access and deletes the stored tokens and, for a team calendar, the calendar list and the stored event titles and times. Events Matter already added to a Google Calendar stay there until you remove them in Google Calendar.
• If Google cannot be reached. Matter still deletes its own copy. You can always remove Matter's access yourself at myaccount.google.com/permissions.
• Deleting your account. Deleting your Matter account (Settings → Account → Delete Account) deletes your Gmail connections and the data synced through them, your own Google Calendar connection, and your chat history. Disconnect your Google accounts first: a team calendar belongs to the team and stays connected until a coach on that team disconnects it, and disconnecting is what asks Google to withdraw Matter's access.
• Asking us to delete it. Email privacy@matterperformance.com and we will delete the Google user data Matter holds for you.

Matter's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

4.9 AI Limitations

AI-generated outputs may be inaccurate, incomplete, or inappropriate. Matter applies deterministic fallback engines and rule-based systems to supplement AI when API calls fail or daily limits are reached (governed by AIRequestGovernor).

5. Data Sharing

5.1 We Do NOT Sell Your Data

Matter does not sell, rent, or trade your personal information or health data to third parties for advertising or marketing purposes.

5.2 Service Providers

We share data with the following service providers solely to operate the Services:

5.3 Coach Access

If you join a coach's team, the coach can see metrics you have chosen to share. You control sharing granularity and can leave a team at any time, which immediately revokes coach access to your data.

5.4 Legal Requirements

We may disclose data if required by law, court order, or governmental regulation, or if we believe disclosure is necessary to protect the rights, property, or safety of Matter, our users, or the public.

5.5 Business Transfers

In the event of a merger, acquisition, or sale of all or a portion of our assets, your personal information may be transferred as part of that transaction. We will notify you of any such change in ownership or control of your personal information.

6. Data Storage and Security

6.1 Where Data Is Stored

• Your device (iOS): Locally, AI response caches (UserDefaults), authentication tokens
• Supabase cloud (AWS): Account data, health daily metrics, sleep stages, workout records, wearable data, team data. Hosted in the United States.
• Wearable provider servers: Your data on WHOOP, Polar, and Apple platforms is governed by their respective privacy policies

6.2 Security Measures

• All data in transit is encrypted via TLS 1.2+
• Supabase database access is controlled by Row Level Security (RLS) policies ensuring users can only access their own data
• OAuth 2.0 for third-party wearable authentication
• Wearable tokens are stored encrypted in Supabase
• Edge functions use secure environment variables for API keys and secrets
• AI request governance limits API call frequency to prevent abuse

6.3 Data Breach Notification

In the event of a data breach that affects your personal information, we will notify affected users and relevant authorities within 72 hours as required by applicable law.

7. Data Retention

8. Your Rights

8.1 All Users

You have the right to:

• Access your personal data (export your health data from the App)
• Correct inaccurate personal data (update your profile in App settings)
• Delete your account and personal data (via App settings or by emailing contact@matterperformance.com)
• Withdraw consent for health data collection (revoke HealthKit permissions in device settings)
• Disconnect third-party wearables at any time
• Disconnect Gmail or Google Calendar at any time, which deletes the Google data Matter stored for that connection (see section 4.8)
• Leave coach teams to revoke shared data access

8.2 European Economic Area (EEA) Residents — GDPR

In addition to the above, you have the right to:

• Data portability — receive your data in a structured, machine-readable format
• Restrict processing — request we limit how we use your data
• Object to processing — object to processing based on legitimate interests
• Lodge a complaint with your local data protection authority

Our legal basis for processing your data:

• Consent — for health/biometric data collection (Apple HealthKit permissions, wearable OAuth)
• Contract performance — for providing the Services you signed up for
• Legitimate interests — for service improvement using aggregated, de-identified data

8.3 California Residents — CCPA/CPRA

You have the right to:

• Know what personal information we collect, use, and disclose
• Delete your personal information
• Opt-out of sale — we do not sell personal information, so no opt-out is necessary
• Non-discrimination — we will not discriminate against you for exercising your privacy rights

California residents may submit requests to: contact@matterperformance.com

9. Children's Privacy

Matter is not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that we have collected data from a child under 13 without parental consent, we will delete that data promptly.

Users between 13 and 18 must have parental or guardian consent to use the Services. Coaches are responsible for ensuring that minor athletes on their team have appropriate consent.

10. International Data Transfers

If you access the Services from outside the United States, your data will be transferred to and processed in the United States. We rely on Standard Contractual Clauses (SCCs) and other lawful transfer mechanisms to ensure adequate protection for international data transfers.

11. Third-Party Links and Services

The Services may contain links to third-party websites or integrate with third-party services. This Privacy Policy does not apply to those third parties. We encourage you to review the privacy policies of:

• Apple Privacy Policy
• WHOOP Privacy Policy
• Polar Privacy Policy
• Google Privacy Policy
• Supabase Privacy Policy
• OpenAI Privacy Policy
• Anthropic Privacy Policy

12. Cookies and Tracking

The Matter App does not use cookies. The Website may use essential cookies for functionality (session management, preferences). We do not use advertising cookies or third-party tracking pixels.

12.1 Research demo

The public demo at /demo/research records, unless you choose “Don't record”: which steps and screens you open (events), the ratings you give, and any feedback you type. A name, email and organization are stored only if you choose to leave them.

• Personal links. A link we sent you personally carries a code tied to your name, email and organization, so your visit is linked to you.
• Notification email. Each rating, answer and follow-up request is emailed to Matter's research inbox. Nothing is emailed to you.
• Chat in the demo. Messages typed in the demo are saved on the shared demo account, and later visitors may see them.
• Retention. There is no automatic time limit on this data yet. To have your research demo data deleted, email privacy@matterperformance.com.

13. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated through the App or by email. The “Last Updated” date at the top of this policy indicates when it was last revised. Your continued use of the Services after changes take effect constitutes acceptance of the updated policy.

14. Contact Information

Matter, Inc.

For privacy questions or data requests:

• Privacy: privacy@matterperformance.com
• General support: contact@matterperformance.com

For EEA / UK GDPR data rights requests, contact: privacy@matterperformance.com