Draft — pending legal review. This policy is a working draft. It will be reviewed by counsel and finalized before FastMacros is submitted to the App Store or Google Play.

Privacy Policy

Draft last updated: 2 November 2026

FastMacros (“FastMacros,” “we,” “us,” or “our”) helps you hit your daily macro targets by reading your remaining nutrition needs and suggesting food that fits. This Privacy Policy explains what information the FastMacros mobile app collects, how we use it, who we share it with, and the choices you have. We care about health data in particular and hold it to the stricter standards below.

1. Information we collect

Account information

When you create an account we collect your email address and a securely hashed password (or an authentication token if you sign in through a provider). This identifies your account and lets your data sync across your devices.

Food, water, and body data you log

We store the information you choose to enter or track, including:

What you typed when logging, and what you picked

When you log a food, we keep, privately with your account, what you typed or said (for example "coke"), the food we suggested, the food you picked, and whether you later changed the amount or deleted it. We use this to put your usual picks first the next time you log the same thing. When several different people pick the same food for the same words, that match can become everyone's default suggestion — that shared list holds only the words and the food, never who picked it. Searches, barcodes, and nutrition labels we could not find or read are also kept privately, so we know which foods to add next. When you scan a restaurant menu photo, we keep the photo, and the dish names, printed prices, and descriptions we read from it (with the restaurant name you gave), privately with your account, so we can check them. Dishes we confirm — by checking them against the photo, or because another person's scan of the same restaurant agrees — may be added to that restaurant's menu in the app, with nothing that identifies you. No nutrition numbers are kept from the scan, and the menu photo is deleted with your account. These records are never used for advertising, never sold, and are deleted with your account.

Your settings, stored with your account

So your setup follows you from your phone to fastmacros.net instead of asking you to start over, your feature settings are stored with your account rather than only on one device. These are preferences, not measurements: your goal dial, ordering filters, taste and diet preferences, planner setup, your household list if you add one (the name and macro targets of each person you add, who may include children), how many adults and kids you cook for (set in cook mode — a count only, never a name or an age), display choices, and health-related feature modes — including whether GLP-1 support mode is on. Your weekly dose-day reminder is included: the day and time you chose and, if you typed one, the optional medication label you gave it — so the reminder you set up on your phone is still yours on your next device. We never suggest a dose, a medication, or a schedule; the label is text you wrote and we only store and show it back to you. A setting reaches a device that has never set it, and a later change on one of your devices reaches the others: when a setting changes in two places, the change our server received last wins. A later change that turns the dose reminder or GLP-1 support mode off also stops the reminder on your other phones once they next open the app, and low-key numbers, once on, is never turned off by another device. These rows are protected like everything else in your account (only you can read them) and are deleted with your account. Your reproductive-health answer is deliberately not included and never leaves your device.

GLP-1 daily check-ins

If you use GLP-1 support mode, the daily check-ins you record are stored with your account rather than only on the device you logged them on, so your history, your patterns view, and the report you can print for your clinician still work when you sign in somewhere else. Each check-in holds what you tapped that day: appetite, energy, food noise, and any digestive symptoms. Only you can read these rows — they are never shown to anyone else, never used for advertising, and never sold — and they are deleted with your account.

Progress photos and body measurements

If you use the optional progress-photo feature, the photos and body measurements you add are private to your account. Photos are stored in a private, per-user location and are only ever shown to you through short-lived links; we never make them public and never share them with any third party, use them for advertising, or use them to train any AI model. You can delete any entry at any time, and when you delete your account (see Section 6) your progress photos and measurements are permanently removed along with the rest of your data.

Health data we read from Apple Health and Android Health Connect

With your explicit permission, FastMacros reads data from Apple HealthKit (iOS) or Android Health Connect so we can calculate what's left in your day and personalize your targets. Depending on the features you use and the permissions you grant, this can include:

We request only the data types the features you use actually need, and you can grant or revoke each permission at any time in your device's Health settings. FastMacros can also, if you turn it on, write foods and water you log back to Apple Health / Health Connect; this write-back is off by default.

Some of these readings are also stored on our servers as part of your daily history, so your trends and targets work across your devices: per day, we retain active energy burned, sleep duration (total minutes, never sleep stages), body weight, body-fat percentage, and lean body mass. These rows are protected like everything else in your account (only you can read them) and are deleted with your account. Hydration, HRV, and resting heart rate stay on your device and are not stored on our servers.

Location

To show restaurants and stores near you and compute distances, the app uses your device's location (precise when you allow it, otherwise approximate) while you use those features. It is sent only for that lookup and is not saved to your account. You can decline location access and still use the rest of the app; nearby suggestions simply won't appear.

Grocery accounts you connect

Most ordering and grocery links simply open the other service in your browser or their app. Kroger is different, and we want to be precise about it. If you connect a Kroger account — Kroger, Fred Meyer, Ralphs, King Soopers and their other store banners — FastMacros works with Kroger's own developer API on your behalf, without you leaving the app. Specifically:

The prices and product details Kroger returns are shown to you while you're using the feature and are not stored in our database. Your Kroger token and store choice are removed from your device when you sign out of FastMacros or delete your account.

For the other grocery retailers we can show prices for, we use price information we have gathered separately — we do not connect to your account, and nothing about you is sent to them.

Photos and descriptions you submit

If you use photo logging, menu scanning, label scanning, or the “describe a meal” feature, or import, adapt, or draft a recipe from a description, the photo or text you submit is sent to be analyzed so we can recognize the food or read the recipe. See Section 4 for the third-party AI providers involved and the consent we ask for first.

Package photos you scan

When you scan a product, you photograph the package — its front and its Nutrition Facts panel — and then its barcode, if it has one. We read the printed words and numbers from those photos (using the AI provider described in Section 4) and show you what we read to check. For every scan that reaches that check, we keep the product photos privately, together with what we read from them and anything you typed in, with your account — whether or not you log the food, and whether or not the package has a barcode. Only your account can add to or view that storage. We keep them so we can check the product’s numbers and add products that are confirmed to FastMacros. The photos are never shown to other users, never used for advertising, and never sold. What we read from them is not used for advertising either; we don’t sell it, and we would ask you before that changed. Please photograph only the package, not people or anything personal. A product you scanned is shown to other users only after an independent check agrees with it — another person’s scan of the same barcode, or a published product record for it (such as USDA’s or Open Food Facts’) — and what they see is the product’s name and numbers, never your photos or who scanned it. A scan with no barcode is not shown to other users. We keep your scans until you delete your account; deleting your account (see Section 6) deletes your scans and their photos.

Credit for what you add. The number of package scans and restaurant menu photos you have added (and how many were confirmed) is shown on your profile, and on your public creator page only if you have made that page public — just the counts, never which products or restaurants.

Subscription and purchase information

If you subscribe to FastMacros Plus or Pro, your purchase is processed by Apple or Google. We do not receive or store your full payment-card details. We do receive subscription status (for example, whether your subscription is active or in a trial) so we can unlock the features you paid for.

Device and usage information

We keep limited operational records needed to run the app — for example counts of how often you use a feature that calls an outside service, so we can apply fair usage limits.

We also record a small, fixed set of product events, so we can see where people get stuck and whether people come back. There are twenty-six of them: that an account was created; that you viewed a setup step, and which number it was; that you finished setup, and whether you completed the questions or chose "Set up later"; that your targets were saved, and what set them (you, the wizard, or an adaptive adjustment); that a food was logged, and by which method (search, photo, description, barcode, label, recipe, or a one-tap card); that the app found you at least one matching order on a given day, and on which screen, recorded at most once per screen per day and never as a count of how many times; that you opened the upgrade screen, and which plan it showed; that a purchase went through, and which plan and billing period; that you opened the review screen for a restaurant chain's order, and on which screen; that you opened a link to go and order, which service it pointed to (the restaurant's own site, DoorDash, Uber Eats, or Grubhub) and the match score we had shown for that order; that a link to go and order failed to open, and which of those services it pointed to; that an order was placed, and whether it was delivery or pickup; that you opened your list of past orders, and nothing else about it; that a week of meals was filled in the planner, which planner it was, and whether the app filled it for you or you asked it to; that you shared a recipe, and only whose recipe it was — one of ours, your own, another member's, or a shop-bought item nobody wrote — never which recipe and never who you shared it with; that you opened "Scan a product", which of its steps you finished (the front of the package, the Nutrition Facts, the barcode), whether the scan ended with a log and whether it had a barcode, or at which step you closed it — never the product, the barcode or anything the label said; that you chose a photo of a barcode from your library, and only how reading it went (a barcode was found, none was, the photo showed more than one, it could not be read, the library did not open, or you cancelled) — never the photo or the barcode; that you earned a free day of membership for scans that added a product we didn't have or whose label showed different numbers from our food records, and which plan it was for; that you searched for food with smart search, recorded at most once each time you open the food search, and only how it went — whether related foods showed or, if not, which kind of reason (for example, that the search named an allergen, diet or “without”, or that nothing related enough was found), whether smart search was ready, turned off or unable to run on your phone, roughly how long the search took, and whether you logged one of the related foods — never what you typed or which food; that the setup screen for health sync, AI features and smart search opened, which of those three you turned on from it and whether that worked (for example, that the health permission was not given or that smart search is waiting for Wi-Fi), or that you closed it with one of them still off — nothing else; that your phone replaced its copy of your rewards with your account's corrected copy after we fixed a counting mistake, and only whether there was a note to show you — never a coin count, a streak or a trophy; that you opened the app on a given day, recorded at most once per day and never as a count of how many times; and that you tapped one of our notifications, and which kind it was (meal-prep day, order-week day, weekly planning day, a repeat-order reminder, a meal reminder, a cook timer, a daily log reminder, an eating window opening, an eating window closing soon, a fast beginning, or a fast check-in). A tap on a medication reminder is counted only as a tap, never by its kind.

None of these name a restaurant, a dish, or a recipe. The ordering records say which delivery service a link pointed to — never which restaurant you were looking at, and never what was in the order. The match score is a percentage describing how well an order fit the macros you had left; it is not a macro, a target, or a measurement of you, and nothing about your body can be worked out from it.

The last two — the app-open record and the notification record — are how we tell whether people are still finding the app useful after the first week. They record the day and the kind, never the content: an app-open record says only that the app was opened that day, and a notification record says only which kind was tapped — not its title, not its text, and not what it was about.

These records never include what you ate, your weight or body composition, your targets, anything you typed, or any search you ran. They cannot: each event may only carry values from a fixed list written into the app, so there is no way for a food name, a number you entered, or free text to end up in one. We keep them in our own database, we never sell them, and inside the app we use no third-party analytics or advertising network. They are deleted with your account.

Separately, the public pages of fastmacros.net (like this page, About, and the tester page) use our hosting provider's visit counting and page-speed measurement (Vercel Web Analytics and Speed Insights) so we can see how many people visit them and how fast they load. It is cookieless and aggregate — page counts and performance numbers, not profiles — and it does not run inside the app or on any signed-in screen, so it never sees anything about your food, health, or account.

2. How we use your information

We use your information only to run and improve the app's features, specifically to:

We do not use your health data for advertising, and we do not sell your personal information.

3. Health data — special commitments

Because health data is sensitive, we hold it to stricter rules:

4. How your information is shared

We do not sell your personal information. We share it only with the service providers needed to make FastMacros work, and only for that purpose:

Content you choose to make public. Your profile is private by default. If you turn it on, your display name, handle, avatar, bio, specialties, published cookbooks, any recipes you have made visible, and your milestone badges become publicly viewable — including on the open web at fastmacros.net. Recipes you publish to the community, and menu corrections you contribute, are shown to other users along with your public name. Comments you post on recipes, and the vote totals they receive, are shown to other signed-in members inside the app — never on the open web. If your profile is private when you post a comment, it shows as "Member", without your name or photo, and stays that way even if you make your profile public later; making your profile private hides your name and photo on all of your comments. Deleting a comment leaves "[deleted]" so replies keep their place; deleting your account removes your name and text from all of them. Who voted is never shown. Your weight, your body composition, your intake, and what you ate are never part of any public page or comment. You can make your profile private again at any time, which removes it from public view.

We may also disclose information if required by law, to protect our rights or users' safety, or in connection with a merger or acquisition (in which case we will continue to protect your information under this policy or notify you of any change).

Separately, FastMacros uses public and licensed reference data — such as USDA FoodData Central, Open Food Facts, OpenStreetMap, and FatSecret — to look up nutrition facts, product photos, and places. When packaged-food results include a product photo, your device loads it from Open Food Facts' image servers (photos are contributor-submitted, CC BY-SA). Looking up a nearby place uses your location; these lookups are not a sale of your personal information.

5. Data retention

We keep your account and logged data for as long as your account is active so your history and progress remain available to you. Product analytics are kept in a limited, rolling window. When you delete your account (see Section 6), we delete your personal data from our active systems within 30 days, except where we must keep limited records to comply with law, resolve disputes, or prevent abuse. Health data read through Apple Health / Health Connect stays under your control in those platforms and is governed by their settings.

6. Your rights & choices

7. Data security

We use industry-standard measures to protect your information, including encryption in transit, access controls, and per-user data isolation (row-level security) in our database. No method of transmission or storage is perfectly secure, but we work to protect your data and to limit who can access it.

8. Children's privacy

FastMacros is not directed to children under 13, and we do not knowingly collect personal information from them. Certain features that involve calorie deficits are additionally restricted to users 18 and older within the app. If you believe a child has provided us personal information, contact us and we will delete it.

9. International users

FastMacros is operated from the United States, and your information may be processed there and in other countries where our service providers operate. By using the app, you understand that your information may be transferred to and processed in those locations, which may have different data-protection laws than your own.

10. Changes to this policy

We may update this policy as the app evolves or the law changes. When we make material changes, we will update the date above and, where appropriate, notify you in the app. Your continued use after an update means you accept the revised policy.

11. Contact us

Questions about this policy or your data? Email us at fast.macros.app@gmail.com.

← Back to FastMacros