MacroWeek privacy policy

Effective date: November 8, 2026. Last updated: November 8, 2026. Version 1.0.

Who we are

MacroWeek is a meal-planning app for iPhone. MacroWeek is developed by Luis Angel Ramirez, an individual developer in the United States, who decides how your data is used ("we" in this policy). Contact: support@getmacroweek.com.

MacroWeek is offered in the United States. If you are a Washington resident, our consumer health data policy explains your rights over health data in more detail.

What we collect and why

We collect what the app needs to plan your week, keep your diary and pantry, and build your grocery list.

Account. When you start, the app creates an account for you with a random account id, and a random id for this installation, used to sync your changes. You need no name or email. If you sign in with Apple, Apple tells us a stable id for you and, if you choose to share them, an email address (possibly a private relay address) and your name. If you sign in with an email code, we keep that email address.
Profile and body details. Your birthdate, the sex used in the energy formula, height, the weight you use for your targets (your weight history stays on your phone), body-fat estimate, activity level, goal, diet style, allergens, foods you dislike, pregnancy or breastfeeding, and your answers to the eating-disorder screening question. We use them to suggest editable calorie and macro targets, to plan meals you can eat, and to keep safety limits in place. Your budget preferences stay in your profile for shopping and planning.
Targets. The calorie and macro targets you accept, and their history.
Weekly check-in (paid). On your phone only, MacroWeek compares the days you marked as fully logged and your weigh-ins with your target and may suggest a bounded change. It never changes a target on its own. The marks, the suggestions you used or kept and your reminder setting stay on the phone and are erased with the app's data.
Meal plan and food diary. The meals you plan and confirm, single foods you log, the nutrition of each confirmed meal, and foods you enter by hand or from a package label.
Meal photos and meal descriptions. If you log a meal from a photo, or by typing or saying what you ate, the photo or the words are read to suggest foods and amounts. Spoken words are turned into text on your phone; the recording never leaves it. Only the foods and amounts you confirm are saved, in your diary. The photo and the words are not kept.
Recipes. Recipes you type or import, their ingredient lines, your approvals and ratings, and the recipe variations you ask for and keep. When you import a recipe from a link, our service opens that one public page once to read its recipe; we keep the link, the date and the author's name with your recipe, and we don't copy the page's photos. When you import from a photo of a recipe card, the photo is read on your phone and never leaves it; only the recognized text is sent, and the photo is deleted once you continue. Your recipes stay private to your account; we never publish them.
Pantry. What you add to your pantry (by quick add, barcode, photo or from your shopping), amounts, where you keep it, dates, what you use, toss or cook, and leftovers. Nothing counts as stock until you add or confirm it.
Grocery lists. The list built from your week and pantry, what you check off and the amounts you change.
Saved stores. When you search for a store to save, what you type goes to Apple Maps. For each store you save: its name, its Apple Maps identifier, your tags for it and the US Census region of its state, plus your organic setting and the products you marked organic. When you save a store, the app adjusts its estimated grocery prices to the average for that store's region. It never learns the store's address or your location from this.
Prices. For each receipt line you keep: the product, the price, the amount, the store you picked and the date. A price you type for a grocery line is kept the same way. Both are used only to estimate your own grocery costs.
Subscription status. If you subscribe, Apple sends us the status of your subscription: the product, its dates, renewals, refunds and the messages Apple's App Store sends about it. We never receive your payment details.
Planning help. If you use planning help, the facts it works from are worked out by MacroWeek for that one request (see AI features) and are not kept.
Your AI choices. Which AI features you allowed or turned off, when, and under which version of the consent text.
AI request records. When an AI feature runs, we keep a record of the request without its content: ids, the feature, the model and prompt version, fingerprints (hashes) of what was sent and received, token counts, timing and the result type. The words and photos themselves are not kept.
Weekly plan calculations. The inputs and results of a weekly plan calculation, kept for up to 30 days so the result can be applied.
App usage events. A short list of screen and button events (for example, that a consent screen was answered). They carry no account id, device id, body, diary, pantry, recipe or grocery content.
Privacy and support requests. When you write to us, we keep a record of the request's type and dates.
Our starter recipes. The starter recipes and pictures MacroWeek provides are not about you.

We do not collect your location, contacts, advertising identifiers or browsing history. A saved store's census region comes from the store's state on your phone, never from where you are. We do not sell your data and we do not use it for advertising.

Where your data goes

Your iPhone. The app keeps a copy of your data in its own storage, excluded from iCloud backup.
Supabase (database and sign-in, in the United States) stores your account and the synced data above, receives app usage events, and keeps daily backups of the database for 7 days. It keeps three kinds of logs, each for 7 days: request logs (your account id with each request), sign-in logs (your account id and, for email sign-in, your email) and database logs (statements and errors, which can carry row ids and never your text).
Fly.io (the MacroWeek service, in the United States) receives your data when it syncs, imports a recipe, calculates a plan, checks a subscription or runs an AI feature, and passes what it stores to the database above. It keeps operational logs that carry your account id, the address of each request and how it went, never what you entered. Fly.io keeps them for 7 days.
Apple provides Sign in with Apple, Apple Health, in-app purchases and the subscription messages from its App Store, and, on your phone, barcode scanning, speech recognition and the reading of receipts and recipe cards. Nothing read on your phone this way is sent to Apple by MacroWeek. When you search for a store to save, Apple Maps receives what you typed.
Anthropic runs MacroWeek's AI features, only for the features you allow (see AI features).
Open Food Facts. When you scan a barcode that the USDA database does not list, the phone sends the barcode number (and nothing else) to Open Food Facts to look up the product.
Store websites. If you tap a store search link on your grocery list (Walmart, Kroger, Instacart), your browser opens that store's site with that item's name. Nothing is sent unless you tap.
USDA FoodData Central. We download public nutrition data from the USDA. Nothing about you is sent.
Email delivery. Signing in with an email code needs a company that delivers our sign-in emails. We name that company here before email sign-in is offered. The same goes for the company that hosts our support mailbox.
A delivery partner is not connected. If that changes, this policy changes first and nothing is sent before.
Analytics and crash-report companies: none. MacroWeek keeps its own short list of usage events and installs no crash-report tool.
OpenAI and Google receive nothing from the app. MacroWeek compares its pantry-photo reading against them only with test photos taken for that purpose, never yours.

No other company receives your data.

AI features

AI features are optional and off until you allow each one. The first time you use one, the app shows what the feature does, that Anthropic processes it, what is sent and what is not. Nothing is sent for a feature you have not allowed, have turned off, or allowed under an older version of the consent text. Your name, email, weight and Health data are never sent to Anthropic, and no account id travels with a request. Not every AI feature is available in every version of the app; a feature you cannot see in the app sends nothing.

What each feature sends:

Pantry photos: the photo you take, with location and camera details removed.
Reading recipe lines: the ingredient lines MacroWeek could not read, and nothing else.
Planning help: plan identifiers and dates, which carry no names or content; the names of the recipes in your week and which days sit inside your range; and facts MacroWeek has already worked out (whether a day is short on protein, your keto and budget settings, which meals are eaten, cooked, locked or leftovers, that you logged food outside your plan today, and how a swap compares). Never your target numbers, weight, diary text or amounts.
Meal photos: the photo of your meal, with location and camera details removed, and the names of the foods it may match.
Describe a meal: only the parts of your description MacroWeek could not read on its own, whether you typed or said them.
Recipe variations: the recipe's title and ingredient names, and the change you asked for.

What happens to results. A result is a suggestion. Nothing is added to your pantry, diary or recipes until you check it. AI never works out a calorie, a target or a price; MacroWeek computes every number itself.

Provider retention. Under its commercial terms, Anthropic does not use what MacroWeek sends to train its models, and it keeps what it receives no longer than 30 days, unless the law or its usage policy requires it to keep something longer. We have asked Anthropic for zero data retention; if it agrees, this section changes.

Turning a feature off. You can turn a feature off at any time in Account and settings. MacroWeek stops sending anything for it right away, cancels a request in progress, drops a suggestion you had not yet checked and, for pantry and meal photos, deletes any photo it was still holding. What you already confirmed stays, and so do the records of your choice and of past requests (see How long we keep it). What was already sent cannot be called back.

Photos

Pantry and meal photos sent to an AI feature travel with location and camera details removed. Our service holds them only in memory while the request runs and never stores them. Your phone keeps the re-encoded copies only until the suggestion arrives, you turn the feature off, or the next launch, whichever comes first. Photos of receipts and recipe cards are read on your phone and never leave it.

Receipts

When you scan a receipt, the photo is read on your phone and never leaves it. You choose which lines to keep. For each line you keep, MacroWeek stores the product, the price, the amount, the store you picked and the date, and uses them only to estimate your own grocery costs. Card and payment details, store-card numbers and points, totals and the rest of the receipt's text are never stored. A price you type by hand is kept the same way as one from a receipt: in your account, used only for your own cost estimates, and erased when you remove it or delete your account. The photo is deleted as soon as you finish or leave the receipt. You can remove a saved receipt at any time; saved receipt prices are deleted with your account.

Apple Health

If you allow it, MacroWeek writes the nutrition of meals you confirm to Apple Health, and removes those entries when you unconfirm a meal or delete your account. If you allow reading your weight, the app imports your weight readings into its own weight history on your phone. The weight you use for your targets, including one filled in from Health, is stored in your account; your weight history from Health stays on your phone. MacroWeek asks Health for no other data and never writes your weight. Health data is never used for advertising and never appears in app usage events, logs or crash reports.

App usage events and logs

App usage events carry no account id, device id or content, and are deleted after 13 months. They travel to Supabase with your sign-in token, so for 7 days Supabase's request logs can link an event to your account; we do not use those logs to do so. Supabase also keeps sign-in logs (your account id and, for email sign-in, your email) and database logs (statements and errors, which can carry row ids and never your text), both for 7 days. Our service's operational logs carry your account id, the address of each request, its result and its timing, so we can keep the service running and look into problems; they never carry what you entered. Fly.io keeps them for 7 days.

How long we keep it

Your account: its random id and, if you sign in, the email, name and Apple id you share: Until you delete your account, then erased.
Profile and body details: Until you delete your account, then erased.
Calorie and macro targets: Until you delete your account, then erased.
Meal plan and food diary: Until you delete your account, then erased.
Recipes you add, import or vary: Until you delete your account, then erased.
Pantry: Until you delete your account, then erased.
Grocery lists: Until you delete your account, then erased.
Your AI choices: Until you delete your account, then erased.
AI request records (ids and fingerprints only): Collected when you use an AI feature. Kept 12 months from the request, then deleted automatically; erased at once when you delete your account.
Weekly plan calculations: Up to 30 days after the calculation finishes, then deleted automatically; at once when you delete your account.
App usage events: Kept without identifiers for 13 months, then deleted automatically.
Apple Health: Only if you allow it. MacroWeek's meal entries in Health are removed when you unconfirm a meal and when you delete your account. Weight readings read from Health stay in MacroWeek's weight history on your phone until you delete them or your account; Health keeps its own copy.
Saved stores and organic choices: Collected when you save a store. Until you delete your account, then erased.
Pantry photos: Collected when you use pantry photos. Your phone keeps the re-encoded, metadata-free files only until your draft arrives, you turn the feature off or the sweep ends (removed at the next launch otherwise); our service holds them in memory only while reading them and never stores them.
Meal photos: Collected when you log a meal from a photo. Your phone keeps the re-encoded, metadata-free files only until your draft arrives, you turn the feature off or the sweep ends (removed at the next launch otherwise); our service holds them in memory only while reading them and never stores them.
Meal descriptions you type or say: Collected when you describe a meal. Kept on your phone only while you review the draft; our service holds the words in memory only while reading them and never stores them. Only the foods and amounts you confirm are saved.
Receipt photos: Not collected: read on your phone and never stored. Deleted from your phone when you finish or leave the receipt, and within 24 hours at the latest.
Recipe-card photos: Not collected: read on your phone and never stored. Deleted from your phone once you continue, and within 24 hours at the latest. Only the recognized text is sent.
Prices from receipts and prices you type: Collected when you keep a receipt line or type a price. Until you remove the receipt or the typed price, or delete your account, then erased.
Subscription status: Collected if you subscribe. Kept until you delete your account, then erased. Messages from Apple about a subscription not yet linked to an account are erased within 30 days.
Crash reports: None collected. No crash reporting tool is installed.
Privacy and support requests: Collected when you write to us. A record of each request (its type and dates, never its words) is kept for 24 months after the case closes, then deleted automatically.
Account deletion record: Collected when you delete your account. Your account id, when you asked and when the deletion finished, kept 8 days, then deleted automatically, so that a restored backup deletes your data again.
Database backups: Daily backups kept 7 days by Supabase; deleted data leaves them within 7 days.
Request and service logs: Supabase request logs, sign-in logs and database logs, and our service's logs, are kept 7 days. Request, sign-in and service logs carry your account id; sign-in logs for email sign-in also carry your email; database logs can carry row ids, never your text.
Our starter recipes and their pictures: Not about you. They stay available until we withdraw them; a withdrawn recipe stays in any plan you already made.
Our staff's reviews of starter recipes: Staff accounts only. Records of our staff reviewing starter recipes carry the staff member's account id. When that staff account is deleted, the id is replaced by a placeholder; the review itself stays.

Deleting your data

You can delete your account in the app: open Account and settings (the gear on Today), then Account, then Delete account. The app tells you what is erased and asks you to confirm. If you signed in with Apple, Apple asks you to confirm with your Apple ID first.

What is erased at once. Your account and everything in it: your profile, targets, diary, plan, recipes, pantry, grocery lists, saved stores, prices, subscription status, AI choices and AI request records, and plan calculations. On your phone, MacroWeek erases its copy of your data, any photos it was still holding, its saved pictures and your sign-in, then starts fresh with a new, empty account. Deletion can't be undone.
If your phone loses its connection after the deletion has started, our servers finish erasing your account within ten minutes.
Apple Health. MacroWeek removes the meal entries it wrote to Health. Your weight readings in Health stay. If MacroWeek can no longer reach Health, you can remove its entries in the Health app, under Apps.
Sign in with Apple. MacroWeek asks Apple to end its sign-in link to your Apple ID. Apple keeps its own records under its own terms.
Your subscription. Deleting your account does not cancel a subscription: billing continues through Apple until you cancel it in Manage subscription. The support page explains how.
What takes longer. Daily database backups are kept 7 days, so your data leaves them within 7 days. If we ever restore a backup, we delete again every account that was deleted after that backup before the service goes back online; for that, we keep a deletion record (your account id and two times) for 8 days. Supabase's request, sign-in and database logs and our service's logs are kept 7 days. Anything an AI feature already sent to Anthropic follows Anthropic's retention (see AI features); Open Food Facts and store websites never received anything tied to your account.
Our staff's reviews. If a staff account is deleted, its reviews of starter recipes keep their content but no longer name the staff member.

Undoing a diary entry or using up a pantry item is recorded as a change: the history stays in your account until the account is deleted. Turning off an AI feature takes effect at once (see AI features).

Your rights

Wherever you live, you can:

See what we hold about you. Write to support@getmacroweek.com and we send you a copy of the data tied to your account.
Correct it. Edit it in the app, or write to us.
Delete it. Delete your account in the app (above), or write to us.
Withdraw your consent. Turn off any AI feature in Account and settings.
Appeal. If we turn down a request, reply to our answer to appeal; we answer the appeal in writing with our reasons within 45 days. If we turn down your appeal, you can contact your state's attorney general (in Washington, the Office of the Attorney General).

We answer every request within 45 days. If we need longer, we tell you why within those 45 days and take at most 45 more. Requests are free. To protect your account, we answer only to the email address on the account, or to a request sent from it. If you use MacroWeek without an account, create one in the app first (Account, then Create an account) so we can tell the request is yours. We never treat you differently for using these rights.

Children

MacroWeek is for adults. You must be 18 or older to use it, and we do not knowingly collect data from anyone younger.

Changes to this policy

When MacroWeek starts collecting something new, sends data to a new company, or keeps data for longer, we update this policy first and change its version and date here. An AI feature that would send something new asks you again before it does.

Versions

1.0, November 8, 2026: first published version.