Privacy Policy

Effective: 2026-11-02

This policy describes how Macroline, operated by Calvert Estate LLC ("we", "us", "our", or the "Operator"), collects, uses, and shares information about you when you use the Macroline iOS app or visit macroline.app (together, the "Service").

1. Information we collect

You give us

• Account information. Email address and a password you create. Passwords are hashed with bcrypt and never stored in readable form.
• Diary entries. Foods you log, the quantity, optional meal type (breakfast/lunch/dinner/snack), the timestamp, and any optional notes.
• Body and goal data. Calorie and macronutrient targets you set, weight entries you log (if any), display name, and timezone.
• Custom foods. Foods you add to your private library that aren't in our public database.
• Body log (optional). If you use the Body log, the entries you choose to record: bowel movements (time and, optionally, Bristol type, amount, ease, whether blood was present, a note), urine entries (time, colour on an 8-shade chart, amount), period days (date and optional flow), daily symptoms (e.g., nausea, bloating, "didn't go"), and the supplements you take with their schedule and when you marked them taken. These are stored on our servers like your diary, used only to show you your own history and observational patterns in your own data (for example, average fiber on days with and without a movement), never used to predict cycles or fertility, never sold or shared, and deleted with your account. Each section can be switched off in Settings → Body log.
• Free-text descriptions. When you use the "Describe meal" feature, the text you submit is sent to our AI provider (Anthropic) for parsing into structured items. The text is not used by Anthropic to train models (per the API terms in effect at the time of this policy).
• Voice input (optional). If you tap the microphone in Describe, your device turns your speech into text: Apple’s speech recognition in the iPhone app, and your browser’s own speech service on the web (Chrome, for example, uses Google’s). We never receive the audio. The text is treated exactly like typed text: it stays on your device until you tap Parse, then goes through Describe as above.
• Customer support communications. If you email us, we keep the message to respond.

Generated automatically

• Authentication metadata. Session refresh-token hashes, the user-agent string from your device, and the IP address of the request, recorded when you sign in or refresh a session. Used to detect compromised sessions.
• Subscription state. Your current tier (Free or Pro), and identifiers from our payment processors (Stripe customer ID, Apple original transaction ID) used to associate your subscription with your account.
• Usage events. Counts of feature use (e.g., "describe meal" call, "barcode scan" call) timestamped per user, used to enforce free-tier quotas. We do not record the content of those events beyond a feature label.
• Product interaction (analytics). To find where people get stuck, Macroline records which screens you reach and a small set of typed facts about them — for example that an onboarding step was viewed, that a search ran and how many results it returned, which way you chose to add food, or that a log succeeded or failed. Each record carries your account id, a random per-session id, your platform and app version, and a timestamp. It is tied to your account, so we can see how a first week actually goes rather than only a total. We never record what you typed: no search terms, no food names, no free text of any kind. This is first-party only — it stays on our servers, is never sent to an advertising network, analytics vendor or data broker, and is deleted with your account.
• Server logs. Standard request logs (URL, status code, timing) retained for up to 30 days for debugging and security.

Apple Health (HealthKit)

If you connect Apple Health (More → Apple Health in the iPhone app), Macroline works with five types of Apple Health data: body weight (HKQuantityTypeIdentifierBodyMass), and, for reading only, body fat percentage (HKQuantityTypeIdentifierBodyFatPercentage), lean body mass (HKQuantityTypeIdentifierLeanBodyMass), step count (HKQuantityTypeIdentifierStepCount) and exercise minutes (HKQuantityTypeIdentifierAppleExerciseTime). Each is a separate switch:

• Write: when "Mirror weight logs" is on, a weight you log in Macroline is also written to Apple Health, sourced as "Macroline."
• Import: if you turn on Import weight from Apple Health, the body-weight readings you allow Macroline to read are copied into your Macroline weight log, stored on our servers like a weight you enter yourself. Turn the import off any time; weights already imported stay in your log until you delete them.
• Import body composition: if you turn on Import body composition, the body fat percentage and lean body mass readings you allow Macroline to read are copied into your Macroline weight log and stored on our servers, the same way. Macroline never writes these two types to Apple Health. Turn the import off any time; readings already imported stay in your log until you delete them.
• Import steps and workout minutes: if you turn on Import steps and workout minutes, Macroline reads your daily totals of steps and exercise minutes (one number of each per day, not individual workouts or locations) and stores them on our servers to show them on Today. They never change your calorie goal. Macroline never writes these two types to Apple Health. Turn the import off any time; you can then remove the days already imported from the same screen.
• Nothing else from Apple Health is read.

Apple Health data is not sold, not shared with third parties, and not used for advertising or other use-based data mining. Imported weights and body composition readings are part of your weight log, and imported daily steps and exercise minutes are part of your activity record, so they appear wherever those do: in the app, on the web, in the Home Screen widget if you add one (see below), and to an AI assistant only if you connect one. You can revoke access at any time in iOS Settings → Health → Data Access & Devices → Macroline.

Home Screen widget (iPhone)

If you add a Macroline widget to your iPhone Home Screen, the app keeps a small summary of today on your device so the widget can show it: water, protein and fiber against your goals, and, if you import them from Apple Health, today’s steps and workout minutes against your goals. The summary stays on your iPhone, in storage that only the Macroline app and its widget can read. It is not sent to us or to anyone else. It is replaced each time Today updates and erased when you sign out. Anyone who can see your Home Screen can see what the widget shows, so remove the widget at any time to stop showing it.

AI assistants via the Claude connector (MCP)

Macroline operates an MCP (Model Context Protocol) server at api.macroline.app/mcp. If you choose to connect an AI assistant such as Claude to your Macroline account, the assistant authorizes with OAuth 2.1 + PKCE and receives a scoped access token tied to your user.

The token grants only the scopes you approve on the consent screen. As of this policy the available scopes are:

• read:foods — search the food database.
• read:diary — read your diary entries, daily summaries, goals, weight entries and body composition readings, water, exercise logs, daily steps and exercise minutes, saved meals, and (if you use them) your Body log, symptom logs, and medication/supplement and dose records.
• write:diary — add diary, exercise, water, weight (with any body composition you report alongside it), Body log, symptom, and medication/supplement entries, and delete individual entries.
• write:goals — update your calorie and macro targets.
• write:foods — add a food to the shared food database.

Weights, body composition readings, and daily steps and exercise minutes you imported from Apple Health are covered by read:diary, exactly like data you entered yourself. No other HealthKit data, no subscription/billing data, and no authentication credentials are exposed through any MCP scope. The connector cannot delete account-level data or change your password.

When you ask Claude to "log a meal" or "show me last week's protein," the request flows: Claude → Anthropic's servers → Macroline's MCP server (server-to-server, bearer token) → your account data → response back through the same path. Anthropic processes only the conversation content you submit to Claude (which may include data Claude has retrieved from Macroline). Anthropic does not bulk-export your Macroline data; the data flow is request-by-request, scoped to the active chat. Anthropic's handling of that content is governed by their own privacy policy at anthropic.com/legal/privacy.

You can revoke connector access at any time. From Claude: Settings → Connectors → Macroline → Remove. From Macroline: sign in at my.macroline.app, Settings → Connect to Claude → Disconnect. Disconnecting invalidates that connection's access and refresh tokens immediately; any future tool calls fail until you re-authorize. Resetting your password disconnects every connected assistant.

What we do NOT collect

• Apple Health data other than the body weight, body composition, and daily steps and exercise minutes you choose to import (see above).
• Health data types other than body weight, body fat percentage, lean body mass, step count and exercise minutes (we do not request access to active energy, basal energy, water, workouts, heart rate, or any other HealthKit type at this time).
• Location.
• Contacts, calendar, or other on-device personal data.
• Photos beyond images you take or pick inside the app for food scanning.
• Advertising identifiers (IDFA). We do not run advertising.
• Cross-app or cross-site tracking data.

2. How we use information

• Operate the Service. Authenticate you, store your diary, calculate daily macro/calorie totals, send transactional emails (signup confirmation, password reset).
• Personalize. Apply your goals to dashboards and summaries.
• Improve the Service. Work out which features get used and where the product confuses people, so we can fix it. We report these in aggregate, but the underlying records are tied to your account (see “Product interaction” above) — we would rather say so than call them anonymous when they are not. We do not use your individual diary content to train AI models.
• Communicate. Send service updates, security notices, and replies to your support requests. We may also send an occasional note about your use of Macroline — for example, one note after your first day of logging if you haven’t logged since. Every note like that has an unsubscribe link. Account emails (signup confirmation, password reset) don’t, because you asked for them.
• Detect and prevent abuse. Block fraudulent signups, payment fraud, and unauthorized access.
• Legal compliance. Respond to lawful requests, enforce our Terms.

3. Who we share information with

We share data with the following service providers strictly to operate Macroline. We do not sell your personal information to anyone.

Each of these vendors has its own privacy policy. We've selected vendors that have public policies and recognized data-protection practices.

We may also disclose information when required by law (subpoena, court order), to enforce our Terms, or to protect the rights, property, or safety of Macroline or others.

4. Where data is stored

Macroline's primary infrastructure is hosted in the United States (Neon Postgres in AWS US-East, Fly.io in IAD region, Upstash US-East). If you access the Service from outside the United States, your information will be transferred to and processed in the US. By using Macroline, you consent to this transfer.

Email and DNS routing pass through Cloudflare's global network. Cloudflare may temporarily process data through edge locations near you for performance.

5. How long we keep data

• Active account data — kept as long as your account is active.
• Server logs — up to 30 days.
• Deleted account data — fully removed within 30 days of deletion request, except where we are legally required to retain certain financial records (Stripe subscription history is retained per Stripe's policy).
• Backups — Neon takes daily automatic backups retained for 7 days. Deleted records may persist in those backups for up to 7 days after deletion.

6. Your rights

You have the right to:

• Access the data we have about you. Most of it is visible in the app (Settings, Diary). For a complete export, email us.
• Correct any inaccuracies. Edit goals, weight, food entries directly in the app.
• Delete your account. Email info@macroline.app with the subject "Delete my data" from the email address tied to your account. We will delete your account, diary, weight history, custom foods, and subscription records within 30 days.
• Export your data. Pro users can export their full diary as CSV from the app. Free users can request a JSON export by emailing us.
• Withdraw consent for processing where consent is the basis (e.g., describing a meal sends text to Anthropic — you can simply not use that feature).
• Stop non-account email with the unsubscribe link in any such email, or by replying to it.
• Object to certain processing or request portability where required by your local law.

For California residents (CCPA/CPRA)

You have the right to know what categories of personal information we collect, to delete your information, to correct inaccurate information, and to opt out of "sale" or "sharing" of personal information. We do not sell or share personal information for cross-context behavioral advertising. To exercise any right, email info@macroline.app. We will not discriminate against you for exercising any CCPA right.

For EU/UK/EEA residents (GDPR)

Our legal bases for processing are: (a) contract — to provide the Service you requested; (b) legitimate interests — to keep the Service secure and improve it; (c) consent — for optional features like meal description text submission to Anthropic; (d) legal obligation — to comply with applicable law. You may lodge a complaint with your local data protection authority. The Operator does not currently appoint an EU representative as we operate below the threshold requiring one; this may change as we grow.

7. Security

Passwords are hashed with bcrypt. All connections to the Service are over HTTPS/TLS. Subscription payment data does not touch our servers — it is handled by Stripe and Apple. Database access is authenticated and role-restricted. We use industry-standard security practices but no system is perfectly secure; if you believe your account has been compromised, contact us immediately at info@macroline.app.

8. Children's privacy

Macroline is intended for users 13 years of age or older. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has created an account, contact us at info@macroline.app and we will delete the account.

Health note for younger users and their guardians. Calorie and macro tracking can intersect with eating disorders. If you or someone you care about is struggling with food or body image, please consider reaching out to a qualified professional. The National Eating Disorders Association helpline (US) is available at 1-800-931-2237.

9. Cookies and similar technologies

The Macroline iOS app does not use cookies. The marketing site (macroline.app) uses Cloudflare Web Analytics, which loads a small script on each page to count visits and record the referring site, approximate country, and browser and device type. It sets no cookies, stores nothing on your device, and does not fingerprint you or follow you to other sites. We do not use third-party advertising or social-media tracking pixels.

A short transparency notice appears on your first visit summarising the above. If you dismissed it and want to re-read it, use the link below — it clears the local flag and reloads the page so the notice shows again. Manage cookie notice.

10. Changes to this policy

We may update this policy as Macroline evolves. The "Effective" date at the top reflects the current version. For material changes, we will notify you by email or by an in-app notice at least 7 days before the change takes effect. Continued use after the effective date constitutes acceptance.

11. Contact

Questions or requests: info@macroline.app

Macroline is operated by Calvert Estate LLC, a Michigan limited liability company doing business as Macroline, which is the party responsible for personal data processed by the Service. Contact us at info@macroline.app.