Metrimeld Privacy Policy
Last updated November 2026.
Metrimeld is available for Mac and iPhone, and is published by Raging Coders. This page explains what data each edition reads, where it is stored, and when it may be sent to a service or a device you choose to connect. If anything below is unclear, email support@ragingcoders.com and we will respond directly.
The short version
- Your data is stored locally in Metrimeld's app storage on your Mac or iPhone. There is no Metrimeld account or Metrimeld server collecting your data.
- We do not run analytics or advertising in Metrimeld, and we do not sell or share your data with anyone for advertising.
- HealthKit access is requested on iPhone only after you choose to enable it. Health data is not sent to third parties or ad networks. If you pair your iPhone with your Mac, selected data is sent directly to that Mac over your local network.
What Metrimeld reads, and why
Metrimeld's purpose is to bring your own nutrition, training, and health data into one dashboard. Depending on which sources you choose to connect, it may read:
- Nutrition and body weight from MyFitnessPal, if you sign in.
- Workout history from Hevy (via an API key you provide) or from a CSV file you export yourself from Strong, FitNotes, or Fitbod.
- Apple Health data on iPhone — body weight and composition, heart rate, HRV, VO2 max, sleep, workouts, steps and other activity, and vitals such as blood pressure, blood glucose, and body temperature — if you grant access in Apple's Health permission prompt. Metrimeld reads this information to display it with your nutrition and training data. Metrimeld does not write data to Apple Health. On Mac, Apple Health data can be imported through a Health.md vault export or its local push API, if you set that up; the Mac app does not read HealthKit directly.
- Clinical records on iPhone, such as laboratory results, from Apple Health if you grant the separate Clinical Records permission. Metrimeld stores the records in your local profile and displays supported results alongside your other health metrics. Clinical records are not sent to Metrimeld or to third parties.
- Camera on iPhone when you choose QR pairing. The camera scans a QR code shown by your Mac to set up a direct connection between your devices. The camera feed is used for scanning and is not recorded or sent to a server.
These sources are optional. Choosing "Use Demo Mode" lets you explore with synthetic sample data and does not connect to your accounts or Apple Health.
Where your data lives
Data Metrimeld reads is stored locally in the app's profile on the device. On Mac, each profile is a separate file in Metrimeld's sandboxed storage. On iPhone, app data is kept in Metrimeld's protected app storage. If you pair an iPhone and Mac, Metrimeld can send selected synced data directly between those devices over your local network; this is device-to-device transfer, not a Metrimeld cloud service.
What leaves your Mac
Metrimeld does not upload Apple Health data or clinical records to Raging Coders, third parties, or advertising networks. Network connections occur only for services you configure or devices you pair:
- Hevy and MyFitnessPal: Metrimeld connects only to fetch your own data from your own account, using credentials or a session you provide directly. For MyFitnessPal, Metrimeld never sees or stores your password — you sign in on MyFitnessPal's own page, and Metrimeld only keeps the session token that sign-in produces.
- Optional AI coaching: off by default. If you supply your own API key for an OpenAI-compatible endpoint, the period you are viewing (a summary of your own nutrition and training data) is sent to the endpoint you configured, so it can write a narrative summary. With no key configured, nothing is ever sent.
- Paired Mac: if you pair your iPhone with a Mac, Metrimeld sends selected health, nutrition, workout, and food data directly to that Mac over your local network so the Mac profile can stay in sync. Pairing is optional and can be removed in the app.
Metrimeld also runs a local MCP (Model Context Protocol) server so AI assistants on the same Mac can answer questions about your own data. It listens on this Mac's loopback address only by default and requires a token to connect; binding it to your local network instead is an explicit, off-by-default setting you control.
What we don't do
- We don't collect your data on a server we operate. There isn't one.
- We don't run analytics or crash reporting that sends your usage or data off your Mac.
- We don't sell or share your data with advertisers or data brokers.
- We don't require an account, sign-in, or purchase to use the app.
Your choices
You can change Apple Health and Clinical Records permissions in iPhone Settings at any time. You can disable syncing or remove a paired Mac in Metrimeld. On Mac, you can delete logged data for a date range, export your data, or delete a profile file. On iPhone, you can remove the app's local profile data using the app's available profile controls or by deleting the app.
Contact
Questions about this policy or your data: support@ragingcoders.com.