I never receive the figures you type in.

This policy explains how weighttimeline.com ("the site") handles information. The site is run by one person, Bibek Sharma ("I", "me"), who is the data controller for everything described here. It is short because there is very little to describe, and the most important claims below are structural rather than promises of good behaviour: the site is a static build with no backend and no database, so most of what a privacy policy usually has to cover simply does not exist here. The exceptions are Google Analytics, which measures anonymous traffic, and Google AdSense, which serves advertisements, both described in full below.

What the calculator does with your inputs

Nothing you type into the calculator ever leaves your device. Your current weight, goal weight, height, age, sex, activity level, daily calorie intake, workout schedule and diet breaks are all processed by JavaScript running in your own browser. The simulation is a single function executed locally; it makes no network requests, and there is no endpoint that could receive the values even in principle.

By default those inputs are not saved either. They live in the page's memory for as long as the tab is open and are gone when you close or reload it, so the calculator starts from its defaults rather than remembering your last session. The exception is the Save button, described next: it is the one way your figures are written down, it only ever writes them to your own browser, and it only runs when you press it.

What is stored on your device

Three things, all of them local to your browser and none of them ever sent to me: timelines you choose to save, your theme choice, and the analytics and advertising cookies described below.

Plans and timelines you save stay on your own device. PressingSave in the calculator writes your figures to a browser local-storage entry named weighttimeline:calculator, so your plans are still there when you come back instead of resetting to the defaults. That entry holds what you typed — current and goal weight, height, age, sex, activity level, calorie intake, workout schedule, diet-break schedule, macronutrient split, units and the date your plan starts.

Some detail worth being precise about. It is written only when you press Save; nothing is stored if you never do. It is local storage, not a cookie, so it is never attached to a network request and cannot be read by me, by Google Analytics, by Google AdSense, or by any other site. And it is readable only by this site on this browser and this device — it does not sync anywhere, which is also why moving plans to another machine needs the Export JSON file described below.

You can remove any timeline at any time through the timeline manager, or clear this site's data through your browser. Exporting as JSON writes a file into your own downloads folder and uploads nothing — the file is yours, and Import reads one back from your device.

Your theme choice. Toggling the theme switch writes a single local-storage entry named theme with the valuelight or dark, so the site does not flash the wrong colour scheme the next time you open it. If no choice is stored, the site follows your system preference. It contains no identifier and never reaches me.

Analytics and advertising cookies. Google Analytics sets first-party cookies on this domain, named _ga and_ga_<id>, holding a randomly generated identifier that lets it tell a returning visitor from a new one. Google AdSense may also set cookies and local identifiers (such as __gads or__gpi) to serve, evaluate and measure advertisements, combat invalid traffic, and personalize ads according to your consent settings. None of these cookies contain the health or body measurements you typed into the calculator.

Analytics

The site uses Google Analytics 4 to measure traffic: which pages are opened, how visitors arrived, roughly where in the world they are, and what kind of device and browser they used. It tells me whether the guides are being read and whether the calculator is worth continuing to build. That is the whole purpose.

What Google Analytics never receives is anything from the calculator itself. Your weight, goal weight, height, age, sex, activity level, calorie intake and results are not sent to it, in whole or in part. There are no custom events, no form-field tracking and no conversion goals wired to the tool. The analytics script observes page views; it is not connected to the simulation.

Google acts as my processor for this and is a separate controller for its own purposes. It receives your IP address as an inherent part of the request, which it uses to derive an approximate location before discarding it, and the random cookie identifier described above. I have not enabled Google Signals, demographic reporting or advertising personalisation in Analytics, and I do not upload any data to it or link it to any other service. What I see in reports is aggregated counts, never a named or contactable individual. Google's own handling is governed by the Google Privacy Policy.

Beyond this, there is no tag manager, no session recording, no heatmaps, no conversion pixels and no social media embeds. I do not fingerprint your device, and I do not track you across other sites.

How to opt out of analytics. Where a consent notice is shown, declining analytics there stops the cookies being set. You can also block the domain googletagmanager.com with any content blocker, install Google's official opt-out add-on, or use your browser's private mode. Blocking it changes nothing about how the calculator works — the tool is fully functional with analytics disabled, because the two are unconnected.

Advertising

The site uses Google AdSense to display advertisements. Google and its partners use cookies and unique device identifiers to serve ads based on your visits to this site and other websites across the Internet.

What Google AdSense never receives is anything from the calculator itself. AdSense has no access to your inputs, saved timelines, or simulation results.

Consent Mode and Personalisation. In jurisdictions where consent is required for advertising storage or personalisation (including the European Economic Area, the UK and Switzerland), advertising cookies and personalisation signals default to denied until you provide explicit consent via a consent management notice. Where consent is denied, ads are served in non-personalised or limited mode. Outside those regions or when consent is given, ads may be personalised to your interests.

How to opt out of personalised ads. You can opt out of personalised advertising from Google at any time by visiting Google Ads Settings. You can also opt out of third-party advertising cookies via the Digital Advertising Alliance (US), the DAAC (Canada), or the European Interactive Digital Advertising Alliance (EDAA).

Third parties

Google (for Google Analytics and Google AdSense) is the third party whose scripts the site loads. Everything else is served from this domain: fonts in particular are downloaded at build time and served from here rather than fetched from a font CDN when you visit, so no stylesheet, font or image request goes to another company.

The other third party is the hosting provider that serves the files. Like any web host, it processes the technical information inherent in delivering a page — your IP address, the URL requested, timestamp, referrer and browser user-agent string — in short-lived server logs used for reliability, security and abuse prevention. I do not use those logs to identify or profile visitors, and neither they nor the analytics data are combined with anything you entered into the calculator, because the calculator's values are never part of a request. Any external link you choose to follow, such as the research references, takes you to a site governed by its own privacy policy.

Your rights

Data protection law, including the GDPR and the CCPA, gives you rights to access, correct, delete and port your personal data, and to object to its processing. Those rights are intact here and are unusually simple to satisfy: there is no account, no profile, no mailing list, and nothing you entered into the calculator for me to retrieve or erase, because I never received it.

The only personal data in play is the analytics and advertising measurement data described above — cookie identifiers and IP addresses Google processes on my behalf or as a controller. Where consent is required, my legal basis is your consent, which you can withdraw at any time by the means listed above; elsewhere the basis is my legitimate interest in funding and measuring the site. I cannot look you up in it, since it holds no name, email address or account, but if you want it removed, email me with the approximate date and time of your visit and I will ask Google to delete the matching records. I do not sell personal information.

If you want to remove everything associated with the site from your own machine, clearing this site's cookies and site data in your browser does it completely — a saved plan, the theme entry and the analytics cookies are all there is. Any plan you exported as a file is in your downloads folder and is yours to delete.

Children

The site is not directed at children under 13, and I do not knowingly collect personal data from them — nothing here asks a visitor's age or identity, and the analytics described above cannot tell me how old anyone is. Weight-management tools are not appropriate for children without professional supervision, and I would encourage a parent or guardian to involve a paediatrician rather than a calculator.

Security

The site is served over HTTPS. Beyond that, the strongest security property here is architectural: data that is never transmitted cannot be intercepted, and data I never receive cannot be breached on my side. There is no database of user measurements to leak, because it was never built. A plan you save is held by your own browser, which makes its security your device's rather than mine — worth knowing if you share a computer, since anyone using the same browser profile can reopen the plan.

Changes to this policy

If this policy changes, the revised version will be published here with an updated date at the top of the page. Were I ever to introduce something that collects more than the analytics and advertising described above — an account system, a mailing list, anything touching the figures you type in — that would be stated plainly here before it shipped, not added quietly to a list of permitted purposes.

Contact

Questions about this policy can go to admin@weighttimeline.com. See also the terms and conditions and the about page, which explains why the engine is built to run locally in the first place.