If you read our privacy policy, you’ll see that it collects total calorie and weight data from users, which we use to improve our adaptive TDEE algorithm. It does not collect email, phone number, date of birth or anything which is not necessary for product improvement/diagnosis.
You can probably achieve something similar with Claude and a bunch of scripts if you log your calories every day.
macrocodex is entirely deterministic, it just works and users don't need to fiddle with it.
Log your calorie each day, log your weight weekly and it will continue producing calorie and macro targets for you to achieve desired rate of weight gain or loss.
It also has many more features, such as lean bulk, cut, and body recomposition modules. It includes a planner that helps you decide when to switch from cutting to lean bulking (or vice versa), or when body recomposition efficiency starts dropping for you.
For example,
To gain least fat while gainng muscles, Lean bulk is what you need.
The key is to focus on your rate of weight gain, not a specific calorie number or surplus percentage.
Weekly Weight Gain Rate:
Beginners: 0.25-0.5% of body weight
Intermediates: 0.25-0.4%
Advanced Lifters: 0.1-0.25%
Usually, a calorie Surplus: +5-10% of TDEE (roughly 100-300 kcal/day) may get you there but if it doesn't adjust your calories up or down to reach the desired weekly weight gain rate.
This is where macrocodex can do better than chatgpt/claude over long horizon.
`datetime | 2500 kcal | 90 kg`
By using Macrocodex, users become part of a shared data pool. They pay nothing, but they can choose to share this data.
We've this data from 17,000+ users that's what makes this accurate.
Data collection on Android can be disabled by turning off Diagnostics under Profile.
The app does not collect anything beyond this, so there is no way to link the data back to any specific person. It does not even ask for your name.
Furthermore, users can easily delete all collected data by going to *Profile > Clear Data*. During onboarding, the app will also show the Health Connect permission request.
On the web app, there is no reliable way to store persistent data because IndexedDB storage can be wiped by the OS or browser. Because of this, it requires backend to save this data.
There are no cookies used on site, no tracking pixels etc...