Marrow
EN
Download

Privacy Policy

Effective October 18, 2026. Updated October 22, 2026: Marrow is now published by Marrow Health LLC. Updated November 1, 2026: this policy now also covers Marrow for Android and Wear OS, and Health Connect.

Marrow is built so that there is almost nothing to collect. Your health data lives on your phone: in Apple Health on iPhone, in Health Connect on Android, and in Marrow's own local database. There is no Marrow account and no analytics. The only copy of your health data on a server we run is the optional Cloud MCP mirror, which exists only if you turn it on and disappears when you turn it off.

The short version. Everything Marrow reads from Apple Health or Health Connect stays on your device. A few things leave your phone, and only when you ask for them: a meal photo, text or voice description you choose to log with AI, a barcode or food name you choose to look up, and, if you turn on Cloud MCP (a Pro feature), a private copy your AI can read. We do not sell data, do not run ads, do not use tracking SDKs (the only analytics we run counts subscriptions, never health), and do not have a way to see your health history even if we wanted to.

This policy covers the Marrow apps for iPhone, Apple Watch, Android and Wear OS, and the services at marrowhealthapp.com and skeletonarmy.tech. Where the two platforms differ, this policy says so. Marrow is published by Marrow Health LLC, a Georgia limited liability company. Questions: [email protected].

1. What stays on your device

All of it, by default. Specifically:

This data is stored in Marrow's local database inside the app's private storage on your phone. Marrow does not store your health data in iCloud or in Google's cloud backup: on Android, Marrow opts its data out of Android cloud backup. If you have iPhone backups enabled, your device backup is governed by Apple's privacy policy, not ours. When you move to a new Android phone with a cable or device-to-device transfer, Android may copy Marrow's data directly to the new phone. It does not pass through us.

2. What leaves your device, and only when you ask

Meal photos you choose to scan

When you log food by photo, that one image is sent to Marrow's photo service and forwarded to Google's Gemini API, which returns a guess at what the food is and its nutrition. Details that matter:

Text and voice descriptions you choose to log

When you log food by typing a description or by speaking, that text or that short audio clip is sent to Marrow's food service and forwarded to Google's Gemini API, which returns a transcript (for audio) and a guess at the foods and their nutrition. The clip and text are held in memory for the request and discarded. Nothing is written to disk on our server. The same Google API terms as for photos apply. No health data and no identity travels with it.

Marrow Coach (Marrow Pro)

Marrow Coach is off until you turn it on in the app, and it can be turned off again in Settings. When you ask it a question, the question and only the numbers an answer needs (for example your last seven days of sleep, or today's meals) are sent to our server and forwarded to Google's Gemini API, which produces the answer. The same Google API terms as for photos apply: the content is not used to train or improve Google's models. Our server holds the request in memory and discards it. It keeps no content from the conversation, only timing, size and token counts for the fair-use limit. The conversation itself lives on your phone for the session and is not stored anywhere else.

Cloud MCP (Marrow Pro): a private copy on our server

This is optional, off by default, and the only case in which we hold health data. When you turn it on, the app creates a mirror on a server we run and keeps it current in the background: your Apple Health or Health Connect metrics, meals, workouts, strength sets, sleep and your daily targets, the same records the app shows. In return, ChatGPT, Claude or Gemini can read that copy any time, including while your phone is asleep. Details that matter:

Purchases

Marrow Pro is sold through Apple on iPhone and through Google Play on Android. The store handles payment, renewals, cancellation and refunds, and we never see your card, your name, your Apple ID or your Google account. The app checks your entitlement with the store on the device. We run no purchase server and keep no purchase records tied to your identity (see Subscription analytics below). When the app talks to our food service it says whether the device is on Pro (one word, so the service can apply the right daily ceiling) and which app version it is. Neither is tied to you.

Subscription analytics (RevenueCat)

To see how Marrow Pro is doing (subscriptions started, kept or cancelled, revenue), the app reports purchase events to RevenueCat, a subscription analytics service. What it receives: the App Store or Google Play transaction (which plan, when, the price tier and whether it renewed), an anonymous identifier RevenueCat generates for the install, and basic device details such as the operating system version and app version. It does not receive your name, email, Apple ID, Google account, or any health data, and we do not use it for advertising. Apple or Google remains the seller. RevenueCat only observes the transactions the store already made.

A version check

Each time Marrow comes to the foreground it downloads a tiny file from our server that says which app versions are still supported. The request carries no identifier. It names only the country of the store your phone buys from (for example USA), and on Android which platform asked, so that prices shown in the app match your store. Our server keeps nothing from it beyond the ordinary connection log described below. If your version is below the minimum, the app shows an update screen instead of running.

Apple Watch and Wear OS

The watch app receives today's totals, your targets and your recent meals from your phone, over Apple's Watch Connectivity on Apple Watch and over the Wear OS Data Layer on Wear OS, and sends back the water and meals you log on the wrist. That traffic stays between your two devices. The watch keeps the latest numbers for its complications and tiles. It reads no health data on the watch itself and holds no health permission. A meal dictated on the watch is turned into words by the watch's own speech recognition and then handled exactly like a typed description above.

Exercise photos

The exercise library's photos are not bundled. When you open an exercise, the app fetches its two photos from a public open-source repository hosted on GitHub (free-exercise-db). GitHub sees an ordinary image request from your IP address and nothing else: no identifier, no health data, and nothing about your workout. The photos are cached on the phone afterwards.

Campus dining menus (Marrow Pro)

If you choose a school, the app downloads that school's published menus from a static file on our server. Your choice of school is stored on your device. The request carries no identifier and no health data.

A random device identifier, for rate limiting only

AI logging (photo, text and voice) and Marrow Coach cost us money per request, so they are capped per device per day: three AI logs a day on the free plan, a higher ceiling on Marrow Pro, and a fair-use budget for the coach. To count requests, the app generates a random identifier the first time you scan, stores it in your Keychain, and sends it with photo requests. It is not your Apple ID, not your device serial, not an advertising identifier, and it is not derived from anything about you or your hardware. Our server keeps only a count for the current day, and yesterday's rows are deleted when the day rolls over. It is never shared, and it is never attached to health data because we never receive health data.

Barcodes and food searches

On Android, barcodes are read on the phone by Google's ML Kit. The camera image never leaves the phone. ML Kit may send Google anonymous metrics about how the scanner performs, which contain no image, no barcode and no health data. When you scan a barcode or search for a food, the barcode number or search text is sent to Open Food Facts, an open food database, to look up branded products. No identifier and no health data goes with it. Marrow also ships with a USDA FoodData Central database built into the app, so generic foods are found offline without any network request at all.

Anything you deliberately export

Marrow's whole point is letting you move your own data. When you export a file, run an automation, pair a server, or connect an AI agent over MCP, your data goes where you tell it to go. If you point an automation at your own server, that server receives your health data and its operator's rules apply. We are not in the middle of that connection, we do not see it, and we cannot retrieve it for you. Choose destinations you trust.

3. What our server logs

The food service writes one line per request containing: a timestamp, how long the request took, the HTTP status code, the size of the upload in bytes, the model name, how many foods were detected, and token counts. It does not log the image, the identified foods, your device identifier, your IP address in application logs, or any health data.

This website. marrowhealthapp.com counts visits with Cloudflare Web Analytics: which pages are viewed, which site sent the visitor, and the browser, device type and country. It sets no cookies, does not fingerprint, and does not follow you to other sites. The app sends nothing to it.

4. What we never do

These are commitments, not defaults we might quietly change. This section exists in part because Apple's App Store Review Guideline 5.1.3 and Google Play's Health Connect policy govern health apps, and we hold ourselves to both explicitly:

5. Apple Health and Health Connect permissions

Marrow reads from Apple Health (iPhone) or Health Connect (Android) only in the categories you approve, and the operating system controls that entirely. You can review or revoke any category at any time: on iPhone in Settings, Privacy & Security, Health, Marrow, on Android in Health Connect, App permissions, Marrow. Marrow also writes back, such as food you log and workouts you record, when you permit it. If you let a connected AI log for you, the entries it adds at your request (including sleep, symptoms and state of mind on iPhone) are written the same way, and only for the types you allow. Revoking a permission stops new reads immediately. Data already synced into Marrow's local database stays there until you delete it or delete the app.

On Android, Marrow asks Health Connect for permission to read data in the background, so automations and widgets stay current while the app is closed, and to read your history beyond the last 30 days, so a first sync can fill your charts. Both are optional and can be turned off in Health Connect.

Health Connect Limited Use. Marrow's use and transfer of information received from Health Connect adheres to the Health Connect by Android permissions policy, including the Limited Use requirements. Health Connect data is used only to show you your own data, to log for you, and to send it where you ask (exports, automations and the AI connectors you approve). It is never used for advertising, never sold, and never used to determine credit-worthiness or for lending.

6. Deleting your data

Delete the Marrow app and everything it stored is deleted with it, since it all lives in the app's private storage. There is no server-side account to close. The one exception is the optional Cloud MCP copy: tap Delete the copy on the Cloud MCP page in Connects before deleting the app and the copy is gone at once. If you already deleted the app with Cloud MCP still on, email us at the address below with your Cloud MCP link (if you still have it) or the approximate date you turned Cloud MCP on, and we will delete the copy within 30 days. We cannot find it by your name, because the copy carries none. Data in Apple Health belongs to Apple Health and is managed in the Health app. Data in Health Connect is managed in Health Connect, where you can also delete what Marrow wrote. Data you exported to your own destinations is yours to delete there. Files you exported to your own devices are, likewise, yours.

7. Security

All network requests use TLS. Paired servers and the on-device MCP server are authenticated with bearer tokens generated on your device and stored in the iOS Keychain or protected by the Android Keystore. The on-device server ships turned off and binds to your local network only when you turn it on, and you can revoke a token by unpairing the server in the app. Cloud MCP works the other way round: its tokens are OAuth tokens issued by our Connect server to the AI you approved (with PKCE, short lifetimes and refresh), stored hashed on the server, and every one of them is revoked by Disconnect. To report a security problem, email the address below with "Security" in the subject, or see security.txt.

8. Children

Marrow is made for adults. On Google Play it is offered to people 18 and older. It is not directed at children under 13, and we do not knowingly collect information from them. We do not have accounts, so we have no way to identify a user's age.

9. Your rights

Under laws such as the GDPR and the CCPA you have rights to access, correct, delete, and port your personal data, and to object to certain processing. Marrow's architecture satisfies these by design: your data is already in your possession, exportable in open formats at any time, and deletable by removing the app. We do not sell personal information, so there is nothing to opt out of. If you believe we hold something about you and want it removed, write to [email protected] and we will act within 30 days.

10. Changes

If this policy changes in a way that affects what leaves your device, we will update the effective date at the top and describe the change in the app's release notes. Continued use after a change means you accept the updated policy.

11. Contact

Marrow Health LLC
[email protected]

See also: Terms of Use and Support.