MacroCodex vs. MacroFactor

MacroFactor asks you to trust its algorithm, entrust sensitive health data and progress photos to its cloud infrastructure, and pay a recurring subscription. MacroCodex gives you a simpler option: test the algorithm for yourself, keep your most sensitive photos off our servers, and pay nothing.

The quick comparison

The short version: MacroFactor asks for more personal information, uploads progress photos, and starts charging after seven days. MacroCodex asks for less, keeps progress photos off its servers, and stays free.

Accuracy and update speed

MacroFactor

Greg Nuckols published a polished algorithm accuracy article filled with charts, interquartile ranges, and correlation coefficients. It looks scientific. The central problem is that it does not test what most readers will assume it tests.

MacroFactor does not compare its algorithm with MacroCodex or another adaptive TDEE algorithm. It compares MacroFactor with a basic TDEE formula. Beating a static population formula after weeks of collecting a user's weight and food logs is a low bar. It cannot support the broader suggestion that MacroFactor is more accurate than competing adaptive apps.

The article also changes the meaning of accuracy. It admits that it is measuring how well logged calories and estimated expenditure explain weight change, not whether the expenditure estimate matches independently measured energy expenditure. MacroFactor even gives an example where a knowingly incorrect expenditure figure earns the better score because it compensates for inaccurate food logging. That may be useful coaching, but it is not proof that the TDEE number itself is accurate.

The test uses 748 people from MacroFactor's own transformation challenge. It excludes users whose logs appear incomplete. This selects unusually engaged users with cleaner data. The article also uses many overlapping periods from the same people in part of its correlation analysis, so those data points are not independent. The article acknowledges this problem but still presents the large correlation as evidence.

Finally, MacroFactor does not publish the underlying user data, the calculated predictions, or a test package that another researcher can run. Nobody outside MacroFactor can check the exclusions, rerun the analysis, change the assumptions, or verify the charts.

So the headline flaw is simple: MacroFactor tested itself, on a selected group of its own users, against a basic formula, using private data and its own definition of accuracy. That is a company benchmark, not independent proof that MacroFactor is the most accurate adaptive TDEE app.

MacroCodex

Our claim is straightforward: MacroCodex produces a more responsive TDEE estimate and, for many users, reaches a useful estimate faster than MacroFactor.

That claim is informed by experience across more than 17,000 users, a MacroCodex community with more than 2,000 members, and a maintained list of more than 120 users who report using both MacroFactor and MacroCodex.

Those reports are not a blinded clinical trial, and we do not pretend that they are. The difference is that testing our claim costs you nothing: use MacroCodex consistently for two to four weeks, compare its estimate with your actual intake and weight trend, and decide from your own data. There is no paywall and no subscription required.

Privacy

MacroFactor

MacroFactor does not merely store calorie totals. Its account based cloud service can combine your real identity with an unusually detailed record of your body, diet, reproductive health settings, goals, and habits.

According to MacroFactor's own privacy notice, it processes:

• Your name, date of birth, and email address
• Your sex and period tracking settings
• Your weight, height, body fat level, and body measurements, including waist, hips, arms, and legs
• Your calorie, macro, and micronutrient intake
• Your weight loss, weight gain, hypertrophy, and strength goals
• Your activity level, exercise frequency, cardio experience, and strength sport experience
• Data imported from Apple Health, Fitbit, Google Fit, or Health Connect when permission is granted
• Your app interactions, preferences, timeline settings, check in behavior, and coaching module choices
• Optional front, side, and back progress photos

These are not speculative accusations. MacroFactor lists these categories itself under MacroFactor App Personalized User Features. Its unified account system stores data under a Firebase user ID and allows both MacroFactor apps to access the data associated with that account; see How Our Apps Work Together.

Put together, this can form an intimate and identifiable personal profile: who you are, when you were born, how your body looks, how much you weigh, what you eat, whether you track your menstrual cycle, what you are trying to change about your body, and photographs documenting that change. Keeping all of it in one cloud account makes a breach, account takeover, or misuse far more serious.

The risk is especially clear with progress photos. MacroFactor says it processes uploaded front, side, and back photos, retains them until the user deletes them or closes the account, and uses Google Firebase/Crashlytics in the United States as a service provider for the feature. See MacroFactor Apps Progress Photos.

MacroFactor says its ordinary support team access excludes progress photos. That is a useful control, but it does not prove that no administrator, privileged employee, contractor, infrastructure provider, compromised account, or attacker could ever access the files. The same section says MacroFactor administrators may access account data when necessary for operations or troubleshooting. It does not clearly guarantee that progress photos are technically inaccessible to every administrator. See MacroFactor Apps User Support and Assistance.

This is the basic cloud storage problem. Access controls reduce risk, but they cannot remove it. A private photo stored in the cloud can be exposed through an account takeover, application bug, administrator account, vendor, backup, configuration error, legal demand, or security breach. MacroFactor says it does not sell personal data and allows deletion. Neither promise removes the risk created when the photo is uploaded. See the summary of its privacy notice.

MacroCodex

MacroCodex asks for less identifying information and refuses to upload the most sensitive category at all. On Android, we do not need to know your name, date of birth, email address, phone number, or postal address to calculate your TDEE. There is no required account connecting your identity to your body data.

MacroCodex may need practical inputs such as age, sex, height, weight, body fat percentage, and nutrition logs to perform its calculation. But age is not a date of birth, and a pseudonymous installation ID is not a name, email address, or phone number. We avoid identity fields that the algorithm does not need.

Most importantly: we do not want your progress photos on our servers at all. The complete disclosure is in the MacroCodex Privacy Policy.

• Progress photos stay local: On Android, progress photos are stored in the app's private storage on the device. MacroCodex does not upload them to its cloud service, diagnostic system, export backups, or web sync. We disable the feature in the PWA because browser storage is not reliable enough for files this sensitive. A photo leaves the app only when the user chooses Android's share option. See Progress Photos.
• Android app data and diagnostics: Profile details and logs are stored locally, but diagnostic collection is enabled by default and may upload app data, including weight, calorie, and imported Health Connect entries, under a pseudonymous installation identifier. Users can disable Diagnostic Data from Edit Profile to stop future diagnostic uploads. See What data the app stores and Diagnostics, crash reporting, and support.
• PWA Cloud Sync: Cloud Sync is optional and available only in the web app. When enabled, synced app data is stored in the cloud and an email address is used for account access and password resets. Android does not require a MacroCodex account and does not collect an email address or phone number. See Cloud Sync and web accounts.
• German and EU hosting protections: MacroCodex stores its own cloud app data in Germany with Hetzner, a German company. This keeps the primary cloud database inside the European Union. Hetzner and its processing are subject to the GDPR and German data protection law. The GDPR sets rules for security, lawful processing, data minimization, processor contracts, breaches, and user rights. This is a stronger choice than placing an identifiable health and photo profile in United States cloud infrastructure. Server location does not decide every legal obligation, and Sentry may process some crash data outside the EU. MacroCodex still keeps its primary cloud app storage in Germany. See Service providers and infrastructure and the GDPR's official territorial scope rules.
• Less identifying information: MacroCodex does not require an Android account and does not collect an Android user's name, email address, phone number, or date of birth. Diagnostic records use a pseudonymous installation ID. This does not make health data risk free, but it removes the most obvious direct identifiers. See What MacroCodex does not do.

Data that never reaches our server cannot be exposed by our server, viewed through our administrative tools, leaked from our database, or handed over from our cloud account. That is a stronger protection than promising that a cloud file is accessible only under limited circumstances.

The difference is simple:

MacroFactor can hold an identifiable cloud profile containing your name, date of birth, email, reproductive health settings, detailed body data, eating history, goals, habits, health platform imports, and progress photos. MacroCodex on Android does not ask for your identity and never uploads your progress photos.

Billing

MacroFactor

At the time of writing, MacroFactor offers only a seven day free trial before payment begins. The trial is tied to an automatically renewing subscription. Unless the user cancels in time, it converts into a paid plan and continues renewing. MacroFactor confirms the seven day trial and automatic renewal in its official pricing information. The Google Play listing says renewal must be canceled at least 24 hours before the current period ends.

Automatic conversion can be easy to miss, especially when seven days is barely enough time for a TDEE algorithm to learn from a user's weight and nutrition history. This “enter billing details now, remember to cancel later” design can lead people to pay simply because they forgot the deadline. Even when disclosed in the store terms, it is a billing tactic users should approach carefully.

MacroCodex

MacroCodex has no seven day countdown, no payment method to attach, no automatic conversion, and no renewal deadline to remember. It is completely free. There is no paywall, subscription, donation prompt, advertising, or payment flow inside the app. MacroCodex never collects your payment card details. It also does not use advertising networks or sell personal data. See What MacroCodex does not do.