Metrimeld Privacy Policy

Last updated August 2026.

Metrimeld is a native Mac app published by Raging Coders. This page explains what data Metrimeld reads, where it is stored, and who — if anyone — it is shared with. If anything below is unclear, email support@ragingcoders.com and we will respond directly.

The short version

• Your data is stored locally on your Mac, in a single file inside Metrimeld's own sandboxed storage. There is no Metrimeld account, no Metrimeld server, and nothing is uploaded to us — because there is no "us" to upload it to.
• We do not run analytics or advertising in Metrimeld, and we do not sell or share your data with anyone for advertising.
• Every third-party connection (Apple Health, Hevy, MyFitnessPal, or an AI coaching provider) is opt-in. If you never turn one on, Metrimeld never talks to it.

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 — 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 — imported through a Health.md vault export or its local push API, if you set that up. (Apple's HealthKit framework is not available to a native Mac app, so Metrimeld does not read Apple Health directly; the app still declares the HealthKit entitlement so this can switch on automatically if Apple makes it available to native Mac apps in the future. No HealthKit permission prompt is shown today.)

None of these connections are required to use the app. Choosing "Use Demo Mode" on first launch lets you explore every screen with synthetic sample data and connects to nothing at all.

Where your data lives

All of the data above, once read, is stored locally in a single SQLite-backed file inside Metrimeld's own sandbox container on your Mac. You can export it, import it, back it up, or move it between Macs yourself — Metrimeld never does this for you without your action. Metrimeld supports multiple independent profiles, each its own local file.

What leaves your Mac

Outbound network traffic only ever goes to a service you have explicitly connected:

• 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.

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

Every source in Settings can be disconnected at any time, which stops Metrimeld from reading it going forward. You can delete logged data for any date range from within the app, export your data at any time, or delete the whole profile file from your Mac to remove everything Metrimeld has stored.

Contact

Questions about this policy or your data: support@ragingcoders.com.