Privacy Policy

Last updated: July 11, 2026

The calculators can be used without creating an account. Calculator results are not saved to the database unless you explicitly choose a feature that requires storage, such as private TDEE history or an email digest preference.

Calculator inputs are passed through the result-page URL so the result can be recalculated in the browser. Result URLs may therefore contain values you entered. Do not enter or share information you consider sensitive.

The contact form sends your submitted name, email, subject and message to the site owner and saves a server-side backup for operational purposes.

BMITDEE uses limited first-party product-use event logging as described below. No third-party advertising or analytics integration is included in this version.

Saved Result History

If you choose to save your TDEE result to private history, the site stores the result values needed to create your progress dashboard, such as date, weight, height, age, activity level, BMI, BMR, TDEE, body fat if provided, and the result link. Your email address is used to send private access links. The stored history record uses an email hash for lookup.

Private history pages are accessed through email-based magic links and are marked noindex so they should not appear in search engines. You can delete saved history from the private dashboard.

Body Trend Visual

The private history dashboard may show an estimated body-shape trend based on saved result data such as weight, BMI, sex, and body fat percentage if provided. This visual is a simplified educational illustration and does not represent a body scan, medical assessment, or guarantee of appearance.

Body Change Explanation

The private dashboard may compare your latest saved result with your previous saved result and generate a brief explanation of changes in weight, BMI, TDEE, body fat percentage if entered, and estimated body visual stage. This explanation is based only on calculator inputs and does not identify exact body-part changes.

Database Storage

Saved TDEE history is stored in a MySQL database on the hosting server. The “Delete my saved history” button deletes saved calculator history, charts, body visual records, and private dashboard tokens. Minimal retained contact and audit records may remain for security, abuse prevention, email-delivery records, and operational integrity.

Adaptive TDEE Tracker data

The Adaptive TDEE Tracker stores entries in your browser’s local storage in this version. The entries are not uploaded to BMITDEE when you save a day, calculate an adaptive estimate, import a backup or generate a local report. You control export, import and deletion. Clearing browser storage, changing devices or using a private-browsing session may remove access to the local record.

Product-use event logging

BMITDEE may record limited first-party events such as opening a product, downloading a dataset or chart, saving a tracker entry, or reaching enough data to unlock an estimate. These events do not include body weight, calorie intake, BMI, TDEE values, notes, email addresses or downloaded-file contents. They are used to understand whether products work and which resources are useful.

Public datasets

Downloads from the Health Data & Media Library are public files. BMITDEE may record the file format and product name when a download is selected, but does not require an account or ask for personal health information to access those files.

Media and publisher requests

When you submit the publisher request form, the contact details and message you provide are used to respond to that request. BMITDEE may log non-sensitive operational metadata such as request type, deadline category, output count and delivery status. The site does not place personal measurements in product analytics.

Developer platform and playground

The public JavaScript SDK modules calculate locally and make no network requests. The API Playground does not send the JSON input or calculation output to BMITDEE. The site may record a non-sensitive event name such as which example function was run, but not the values entered, measurements, notes or generated result.

GitHub issues and public contribution channels should never contain real health records, email addresses, private-history links, server credentials or other personal information.