Cook More Argue Less

Privacy Policy

Version 2026-11-16

This policy explains what Cook More Argue Less collects about you, why, who else sees it, how long it is kept, and what you can do about it. The service is run by Mark Freudenberg ("we") and plans meals for a household: who is home, what everyone will eat, and what to buy. Our guiding rule is to collect only what the app needs to do what you ask of it. We never sell personal information, and we do not track you across other sites. We do not show advertising today; the Advertising section says what we promise if that ever changes.


1. What we collect

  • Your account: email address, display name, how you are related to the household, an optional photo, your role, when you last signed in, and a record of which version of this policy and the Terms of Service you agreed to. Your password is stored only as a one-way hash. If you sign in with Google, we keep the identifier Google gives us for you, the email address and name Google vouches for, and nothing else from your Google account. If you sign in with Apple, we keep the identifier Apple gives us for you and the email address Apple provides, which is your own or, if you choose Hide My Email, a private address Apple forwards to you; Apple gives us your name only the first time, and we use it only to fill in your profile. We also keep, encrypted, a token Apple gives us for your account, only so that we can tell Apple to withdraw its access when you disconnect Apple or delete your account. If you turn on two-step sign-in, we keep your authenticator secret encrypted and your recovery codes hashed. If you add a passkey, we keep its public key and the name you give it; the private key never leaves your device.

  • Your sessions: for each device you are signed in on (a browser, or the iPhone app), its browser or app type and when it was last used, so you can see and sign out devices in You → Devices.

  • Planning data: your weekly availability, the foods you like, avoid or cannot eat (including allergens and dietary restrictions), your household's meal plans, votes, ratings, verdicts, shopping lists, and the recipes you add or import.

  • Health and fitness data, only if you open the Diary and give the separate consent described in our Consumer Health Data Privacy Policy: what you log eating and its nutrition, your weight, your exercise, the details used to work out a calorie target (birth date, sex, height, activity level, goal), and daily summaries from Garmin if you connect it.

  • Notifications: the emails and in-app notices we send you and, if you turn on push notifications, a subscription that lets your browser receive them or, in the iPhone app, the notification token Apple gives that phone. Signing out of the app asks us to remove that phone's token. Timers you start while cooking ring from the phone itself and are not sent to us.

  • Technical records: our server logs each request with your IP address and browser type, to run and secure the service. Your sign-in uses a short-lived token kept in your browser's local storage (the iPhone app keeps it the same way) and a secure cookie that is used only to renew it. We set no advertising or analytics cookies and use no trackers.

2. Why we use it

  • To run the service: sign you in, build and share your household's plan, keep shopping lists and send the reminders you asked for.

  • To keep it safe: prevent abuse, limit repeated sign-in attempts, find and fix faults, and detect accounts that break the Terms of Service.

  • To measure what AI features cost us, per household.

  • To answer your requests and tell you about changes to the service or these documents.

  • We do not use your data for advertising today, we never sell or rent it, and we do not share it with anyone except as this policy says. The Advertising section says what we promise if we ever show ads.

3. Health data, and your separate consent

The Diary, weight, exercise, health target and Garmin features hold health data about you. Some laws give health data extra protection, and we treat it that way: you are asked to agree to its collection as its own step when you first open the Diary, you can withdraw at any time in You → Privacy & data, and nothing is collected for these features before you agree. Other members of your household cannot see it, and neither can a household admin; that separation is tested. Our Consumer Health Data Privacy Policy says exactly what is collected, why, who sees it, and how to use your rights.

4. Who else sees your data

We share data only with the people and services below, and only as far as they need it.

  • Your household. Other members see what planning needs: your availability, votes, verdicts, and the food preferences used to plan meals. A household admin can also view and edit members' food preferences and profile details. Not your Diary or health data.

  • Families you connect with, and the community, as the next two sections describe.

  • An AI provider, only if we have turned AI features on for your household, which for now is only the operator's own household. Where they are on, features that read or write recipes, work out nutrition, or look up a food you typed send only the text needed for that task (a food or ingredient name and amount, or the text of a recipe) to Anthropic, which processes it on servers in the United States. We never send your name, email address, IP address, account identifiers, weight or any other health data. A photo you upload for recipe import is read on our own server; only the text read from it is sent. Before anything is sent we ask for your explicit yes, naming the provider and its country, and we record it with the provider it was for; if the provider ever changes we ask again. You can withdraw at any time in You → Privacy & data, and nothing is sent after that. We record the cost of each AI call (the feature, size and price, never the content).

  • An email service, Resend, which carries the messages we send you (sign-in codes, invitations, reminders, password and security changes, the morning summary of your household's plan). It sees your email address and the message.

  • Google or Apple, if you choose to sign in with them: they tell us who you are and learn that you signed in here.

  • Your browser's push service (run by Apple, Google or Mozilla), if you turn on push notifications in a browser, and Apple's push notification service, if you turn them on in the iPhone app. They carry the notice's title and text to your device, and Apple sees that a notice was sent to that phone.

  • Garmin, only if you connect it: you enter your Garmin sign-in once, we use it to log in and do not store it, and we keep an encrypted token to read your daily summaries.

  • Amazon, only if you link Alexa, as the Alexa section below describes.

  • The person who runs the service has technical access to the database in order to run it, fix faults and answer your requests. We look at household data only for those reasons, and never at Diary or health data except at your request.

  • The law. If a valid legal demand requires it, or to protect someone's safety, we may have to disclose data. We will tell you when we are allowed to.

  • Where it is stored: on a server we run in the United States, with encrypted connections, and backups copied to a separate storage device and from there to an off-site backup.

5. Families you connect with

If your household connects with another household in Families (adults only; nobody under 18 takes part), only that household can see what you choose to send it. Nobody else can, and we do not read it: the one exception is a report, below.

  • What can be sent, each only when your household's admin has turned it on for that family: a copy of a recipe (its name, description, ingredients, times and tags, its steps only if your household wrote them, or the address of a page you saved); your household's one verdict on a recipe (never one person's); and the dinners your household cooks at home from today to the end of next week (dates and dish names).

  • What is never sent: anyone's name or profile, food preferences, allergies, health data, the Diary, availability, notes, who is eating or cooking, nights out or away, or ratings from anyone under 18.

  • What the other family holds is a copy made when it was sent. They cannot read your live recipes or plans. A shared week is replaced each time it updates and disappears when you turn it off or disconnect. A recipe they have already saved is theirs to keep.

  • To connect, a family code, link or an admin's email address is used. A new family can be found by name until its admin changes that in Families settings (to the exact name only, or to the code and link only); searchers see only that name. We email a household's admins when another family asks to connect or accepts, and anyone who turns it on when something is sent; those emails name the family and link back into the app, and never carry the recipe.

  • A report: if you report something you were sent, a copy of it and the reason you give are shown to us, and kept so we can act on it, even after you delete your account. We do not tell the other family who reported it. Apart from reports, we see only counts (how many families are connected, how much is sent), never what was sent.

  • When a household is deleted, what it has sent to other families is removed. Recipes another family already saved stay with them.

6. The community

If your household's admin chooses to share with the community, the recipes your household wrote and chose to share are shown to other households under your family's name, and pages you saved from the web are shown as the page's own public facts with a link back. Nothing else is shared, and your admin can stop at any time. The Community Terms say what other households may do with a copy.

7. Cooking by voice (Alexa)

If you link Alexa (You → Cook with Alexa), Amazon's voice service reads your recipes to you while you cook. This is off until you turn it on, and you can turn it off at any time.

  • What leaves the app: the recipe being cooked, one at a time (its name, ingredients, amounts and steps), what Alexa says about it, and, only if your household has the AI on and you ask a question, the question and the recipe text, which go to our AI provider.

  • What Alexa never gets: your Diary or health data, your shopping list, your plan beyond tonight, other households' recipes or any family connection. The link works for cooking only, and nothing else in the app accepts it.

  • Amazon keeps your voice recordings and transcripts under your own Alexa privacy settings, not ours. We do not receive audio. We keep a record of the link (who linked, when it was last used) and, while you cook, which step you reached, for a day.

  • While the Alexa skill is in testing you can ask for an invitation: you give the Amazon email your Echo uses, we keep it with your account, show it to the person who runs this app, and pass it to Amazon, who send the invitation. You can withdraw the request from You → Cook with Alexa, and it is deleted with your account.

  • Each Alexa account links to one person, and so to one household, and only ever reads that household's recipes. Disconnect from You → Cook with Alexa, or from the Alexa app, and the link stops working at once.

8. The iPhone app

The Cook More Argue Less iPhone app is optional. It shows this same service in an app, so everything above about your data applies to it exactly as it does in a browser. This section covers what is different.

  • Signing in: with your password, a passkey, Google or Apple. Apple's and Google's sign-in sheets are theirs; what we receive from each is described under What we collect.

  • Notifications: only if you turn them on in You → Notifications. iOS asks you first. The phone's notification token is kept with your account so we can send you the notices you asked for, and it is removed when you sign out of the app (we ask for that as you sign out) or delete your account. Timers ring from the phone itself.

  • The camera: only when you choose Take Photo, to photograph a dish or a recipe page. The photo is handled exactly like a photo you upload from your library: a dish photo is kept with the recipe, and a photo used to import a recipe is read on our own server, as described above. The app never uses the camera, or your photo library as a whole, on its own.

  • Keeping the screen on while you cook, and a light tap on buttons: both happen on the phone and send us nothing.

  • What the app does not do: it has no analytics or tracking tools, shows no advertising today (see Advertising), and does not ask to track you across other apps and sites. It collects nothing about you beyond what this policy already lists.

  • Deleting the app does not delete your account. Delete your account in You → Privacy & data, in the app or in a browser.

9. The browser extension

The "Save to Cook More Argue Less" extension for Chrome, Edge and Firefox is optional. It saves the recipe on the page you are reading to your household, as if you had pasted the page address into Add Recipe.

  • It reads a web page only when you press its button, and only that tab: the recipe data the page publishes, the text you selected (or the page's main text if you selected nothing), and the page's main image. It reads no other tab and runs nothing on other sites between presses.

  • What it sends: that page content, and the page's address, to this app, as you, using the sign-in your browser already has with us. The extension itself holds no password or token, makes no network requests of its own, and has no analytics. The content goes through the same import as Add Recipe, so everything above about Add Recipe, including the AI provider, applies to it.

  • To save the recipe it opens this app in a background tab, then closes it and shows a small window on the page you were reading, with a link to review the recipe. On this app's own pages only, it also reads one marker from the page that says whether the save worked, and it sets one marker so the app can tell the extension is installed.

  • It stores two settings in your browser: the app address and whether to save for you. If you use your browser's sync, your browser syncs them. We never receive them.

  • What we keep is the recipe you saved, in your household like any other, and a reminder in your bell to look it over until you open it. Whether the recipe is then shared with the community follows your household's sharing choice, as for any recipe you add.

  • Remove the extension in your browser at any time. The recipes it saved stay in your household until you delete them.

10. How long we keep it, and deleting it

  • Your account, planning data, preferences, notifications and sessions: until you delete your account, then removed from the live service at once.

  • Health data: until you delete an entry, withdraw consent and ask for deletion, or delete your account.

  • Backups: every backup, including the off-site cloud copy of it, expires within 30 days of being made, so a copy of deleted data can survive in one for up to 30 days.

  • Server logs (IP address, browser type): up to 90 days.

  • Apple's token, if you signed in with Apple: kept encrypted until you disconnect Apple or delete your account, when we also tell Apple to withdraw its access.

  • Sign-in codes and sign-up tokens: minutes to hours, then deleted.

  • The AI cost record (feature, size, price; never content): 13 months, and it no longer points to you after you delete your account.

  • Reports you make about shared content, and the record that a recipe was taken down: kept so we can act on them, even after you delete your account.

  • The operator's record of moves between households, merges and two-step resets: kept with the household, without your Diary or health data, until the household is deleted.

  • What you agreed to, and when: deleted with your account.

  • You can delete your account yourself in You → Privacy & data. That erases your profile, preferences, Diary and health data, notifications and sign-in. Your household's meal plans and history stay with the household and are handed to a remaining admin. If you are the only member, the household and everything in it is deleted too. The last admin of a household that still has other members must appoint another admin first. Recipes other households already saved from yours stay with them.

11. Your choices and rights

  • See and correct your profile and food preferences in You; admins can correct household members' details.

  • Download everything we hold about you, as a file, at any time. Household admins can download what the household owns and shares.

  • Delete your account at any time.

  • Withdraw your consent to health data at any time, and ask us to delete it.

  • Turn off emails and notifications in You → Alerts.

  • Write to us to use any of these, or any right your state gives you, if you cannot do it in the app. We answer within 45 days, and if we refuse you can ask us to look again. We honour these rights for everyone, wherever they live; we are not a "business" under the California Consumer Privacy Act, but we treat your requests as if we were.

12. Advertising

The service shows no advertising today. We may show some in the future. If we do, these promises hold, and the Changes section below does not shorten them:

  • We never sell your personal information.

  • Nothing in the Diary or anywhere else about your health, weight, food log or exercise is ever used to choose, target or measure an ad, and no ad is shown in those parts of the app.

  • No ad is shown to an account marked as under 18, and nothing about such an account is used for advertising. We do not ask anyone's age; the household's admin marks who is under 18, as described under Children, and we respect that marking.

  • We tell you, by email or in the app, at least 7 days before the first ad appears, and we say what kind of advertising it is and who provides it. This is the one change we make on 7 days' notice; every other change that matters gets at least 30 days, as the Changes section says.

13. Do Not Track

We do not track you across other sites, and no third party collects information about your activity here for use across other sites. Because we do nothing a Do Not Track signal would turn off, we do not change our behaviour in response to one.

14. Security, and if something goes wrong

Connections to the service are encrypted. Passwords are stored hashed; two-step secrets and Garmin tokens are stored encrypted. Each household's data is separated from every other household's by controls in the database itself, and that separation is tested automatically. No system is perfectly secure. If a breach affects your data, we will tell you and the authorities as the law requires: within 60 days of discovering it under the FTC's Health Breach Notification Rule, and sooner where state law says so.

15. Children

You must be 13 or older to hold an account, and we do not knowingly collect personal information from anyone under 13; if we learn we have, we delete it. A parent or guardian who is a household admin may add a family member who is under 18, or enter food preferences for a family member who has no account. We do not ask anyone their age: the admin marks anyone under 18, and a marked account is shut out of Families, sharing and the Diary completely. The Diary and the other health features are for people 18 and over.

16. Where your data is processed

The service is offered to people in the United States and runs there. Where AI features are on, the AI provider named above processes the recipe and food text sent to it in the United States.

17. Changes to this policy

When this policy changes in a way that matters, we tell you at least 30 days in advance by email or in the app, change the version date at the top, and ask you to read and agree to it again the next time you sign in. Smaller corrections change the date only. The one exception is the start of advertising, which we announce at least 7 days ahead, as the Advertising section says.

18. Contact

Questions, requests, or "this was not me": support@cookmoreargueless.com, or Mark Freudenberg, 945 Taraval St #1091, San Francisco, CA 94116. We are responsible for your data.


Something wrong? Contact support