No AdSense script, analytics service, account system, tracking pixel, or server submission is included in this build. Calculator entries are processed by JavaScript in the user's browser.
Calculator inputs
Age, equation sex input, height, weight, activity answers, body-fat estimate, goal, macro preference, observed intake, and weight trend are used locally to calculate energy results. Food and recipe ingredient names, nutrient values, source metadata, serving weights, cooked yield, meal rows, walking speed, treadmill grade, cadence, and session duration are also processed only in the browser. This version does not transmit those values to Calorie Method or another service.
Local storage
When a user selects “Save locally” on the general calculator, the current result and inputs are stored in that browser using localStorage under the key calorieMethodPlanV1. The data may remain until browser storage is cleared and does not synchronize across devices. The visible “Delete saved” control removes it. The deficit, gain, food, recipe, and calories-burned calculators do not save their entries or rows.
Server logs
Although the site itself does not currently collect submitted data, a future hosting provider may process IP addresses, request times, user-agent information, and requested URLs in routine security and access logs. This policy must be updated with the actual host, retention period, legal basis, and contact details before deployment.
Future Google AdSense use
The site plans to apply for Google AdSense but does not currently load it. If enabled, Google and its partners may use cookies, local storage, device identifiers, IP addresses, and browsing information to deliver, measure, limit, or personalize advertising, subject to applicable law and user choices.
Before activation, the publisher must add the actual legal publisher identity, contact method, jurisdictions served, Google disclosures, partner information, opt-out controls, and an accurate inventory of cookies and purposes. This page is a foundation—not a complete legal policy for an unknown business and audience.
Consent requirements
Google requires publishers serving ads in the European Economic Area, United Kingdom, and Switzerland to use a Google-certified consent management platform that integrates with the IAB Transparency and Consent Framework where required. Consent must be obtained before non-essential storage or personalized advertising where applicable.
Users must be able to revisit their privacy choices. Consent should not be bundled into calculator use, and refusing personalized advertising must not prevent access to the core calculator.
Advertising placement
No advertisement code or reserved advertisement containers are included in the current design. If advertising is introduced later, advertisements must not resemble menu items, calculator fields, result buttons, downloads, or editorial recommendations. The site will not ask users to click ads or place controls where accidental clicks are likely.
Children and sensitive use
The calculator is designed for adults and validates age 18 or older. It is not knowingly designed to collect children's data. It also should not be used for eating-disorder treatment or medical nutrition therapy. If future accounts or remote storage are introduced, a separate data-protection assessment will be necessary.
User choices
Users can avoid local storage by not selecting “Save locally.” The calculator's “Delete saved” control removes the Calorie Method plan from browser storage; clearing site data through browser settings does the same. When advertising is enabled, add consent withdrawal and relevant ad-privacy links here.
Policy references
- Google EU user consent policy guidance
- Google consent-management requirements
- Google ad placement policies
Last updated: August 15, 2026. Replace pre-launch disclosures with jurisdiction-appropriate language reviewed for the actual publisher and deployment.