Your information.
A clearer picture.

Contact MacroMonkey

For questions about how MacroMonkey handles information, email [email protected].

This website

The website has no account system, advertising pixels, analytics scripts, newsletter form or payment form. It does not request your food diary or Apple Health records. The site itself does not set cookies or use browser local storage.

Cloudflare hosts and delivers the website. Requests necessarily send technical information, including an IP address, requested URL and browser information, to the hosting service. Cloudflare may process that information to deliver and protect the site under its privacy policy. This is separate from the app’s local diary.

Following an external link takes you to another service with its own privacy practices.

Your diary and settings

The current app stores the food entries, nutrition values, targets, saved foods, recipes and drafts you add on your device. It uses those records to show your diary, summaries and insights. The app does not require a MacroMonkey account and has no advertising or third-party analytics SDK.

The diary is not synced to iCloud. It is currently excluded from automatic device backup, and there is no in-app restore feature. Deleting the app or moving to a different phone can lose the diary. CSV and JSON exports are readable copies, not restorable app backups. This recovery behaviour is under review before public release.

Camera, photos and estimates

Camera and photo features use the images you choose to capture or select. Text recognition and supported nutrition estimates run on the device. The current app does not silently upload a meal to a remote AI service when an on-device model is unavailable.

Meal-estimation images are transient; saved estimate details contain text and nutrition values. Recipe-scan drafts can retain selected scan pages on the device while you finish the recipe. Estimates are editable and require review before saving.

Recipe websites and food providers

When you import a recipe link, your device requests that webpage directly. The website you chose receives the request and its technical information. The import uses an ephemeral session without a persistent cookie or credential store.

External food search and barcode catalogue lookup are not enabled in the current release configuration. Development builds can query Open Food Facts, sending the search text or barcode and request information to that service. This policy will be updated if a production provider is enabled. Manual and saved-food logging do not require an external food catalogue.

Optional Apple Health sharing

If you authorise it, MacroMonkey writes selected, confirmed nutrient values to Apple Health. It does not read Health records. You choose the nutrient types and can pause sharing or change permissions. Pausing does not remove samples previously written; manage those in Apple Health.

Widgets, sharing and reminders

Widgets use a protected local summary containing aggregate nutrition figures, not food names or photos. The share extension can store recipe links or text in a local inbox for the app to review. Reminders are optional local notifications, not remote push messages.

Development recipe-sync trial

Production recipe sync is disabled. A separate, opt-in development trial can copy selected ordinary recipes and appearance settings into a private Apple CloudKit container using encrypted payloads. It excludes the diary, targets and Health data. Disabling that trial does not erase existing local or cloud copies; its revision history is retained for conflict recovery. It is not a diary backup service.

Your choices and copies

You can edit or delete local records through the app, discard drafts and export a selected diary period. Exported files remain wherever you choose to save or share them, under that destination’s controls. Apple Health samples and development CloudKit copies have the separate behaviour described above.

Contacting support

If you email support, you choose to share your email address and message contents. They are used to respond to your request. Keep unnecessary sensitive information out of your message; you can ask for support correspondence to be deleted, subject to any applicable retention obligations.

Changes to this notice

Updates will appear on this page with a revised date. Material changes to app features or data handling should be reflected here before those features are made publicly available.