WHOOP reviewer UX artifact

MacroMate WHOOP integration design

MacroMate plans to integrate WHOOP as an optional Profile/Settings connection that helps Mac Chat answer relevant food-ordering and nutrition questions with recent recovery, strain, sleep, and workout context.

User experience flow

WHOOP is not presented as a dashboard or workout tracker. It is a quiet connection controlled from Settings and used only when it can improve Mac Chat's answer to a relevant nutrition question.

1

Settings entry

Premium or active-trial users open Profile/Settings and tap Connect WHOOP.

2

MacroMate consent

MacroMate explains that WHOOP data will be used to personalize Mac Chat food and nutrition answers before opening WHOOP OAuth.

3

WHOOP OAuth

The user grants permission in WHOOP. The callback exchanges the authorization code server-side; the client secret never ships in the mobile app.

4

Connected state

Settings shows WHOOP / Connected. A manage sheet lets the user disconnect WHOOP from the same surface.

How Mac Chat uses WHOOP data

Relevant questions only

Mac uses WHOOP context for prompts like "I just had a long swim, what should I eat?" or "I slept badly, what is a good recovery meal?"

Compact summaries

The backend fetches recent WHOOP data and builds a short summary for Mac. Raw WHOOP JSON and OAuth tokens are not sent to the model.

No unrelated surfacing

If the user asks a normal restaurant macro question, Mac does not need to mention WHOOP or show WHOOP-derived context.

Requested scopes

MacroMate requests read-only WHOOP access for the data needed to make post-workout, recovery, sleep, and strain-aware food recommendations. Profile access is used only for connection/account metadata in the OAuth integration flow.

read:recovery read:cycles read:sleep read:workout read:profile

MacroMate does not request read:body_measurement, does not write WHOOP data, and does not use WHOOP data for ads, attribution, marketing, resale, or model training.

Data handling and controls

Server-side token handling

  • OAuth tokens are exchanged by Firebase Cloud Functions.
  • WHOOP tokens are encrypted with Google Cloud KMS before storage.
  • Mobile clients cannot read stored WHOOP token documents.

User controls

  • Users opt in from Settings.
  • Users can disconnect WHOOP from Settings.
  • Account deletion and support requests cover stored integration data.

Product boundaries

  • No WHOOP dashboard.
  • No workout tracker or recovery coaching UI.
  • No notifications triggered by WHOOP data.

Implementation status

This WHOOP integration is planned for an upcoming MacroMate release. The release scope is deliberately small: connect in Settings, show a connected state, allow disconnect, and let Mac Chat use compact WHOOP context only when the user's question calls for it.

Questions can be sent to support@macromatefastfoodhacks.com. MacroMate's current privacy policy is available at macromatefastfoodhacks.com/privacy.