Privacy Policy

Overview

This Privacy Policy applies to Body Type Calculator and the pages published under bodytypecalculator.org. In this policy, “we,” “us,” and “our” refer to the operators of the site. “You” refers to any visitor, reader, or user of the site’s calculators and guides.

The site is designed to answer practical body-measurement questions with as little data collection as we can reasonably get away with. The calculators are front-end tools, not account-based services. There is no requirement to register, log in, or create a profile before using them. That design choice is a privacy decision as much as a product decision.

At the same time, privacy is not the same as invisibility. When you load any website, your browser has to request files from a server or CDN. When you email us, your message necessarily contains information you chose to send. When you save a result locally or generate a shareable link, your browser may store or display data on your own device. This policy explains those realities in plain language rather than pretending the site is doing nothing at all.

Information We Collect

Information You Provide Directly

The clearest example of information you provide directly is email correspondence. If you send us an email or use the contact page to prepare an email message, we receive whatever contact details and message content you choose to include. That can include your name, email address, page URLs, technical questions, screenshots, correction notes, or other context you decide is relevant.

We do not require you to send body measurements when contacting us, but many users choose to include them when asking why a result looks borderline or whether a measurement was taken correctly. If you send us those numbers voluntarily by email, we will receive them as part of your message. In other words, the site does not harvest measurements behind the scenes, but correspondence you initiate can still contain personal or sensitive context because you put it there yourself.

A second category of direct input exists entirely on your own device: measurements entered into the calculators and guides. These values are typed by you, but under the site’s current implementation they are normally processed in the browser rather than submitted to us. They become information we receive only if you deliberately share them, email them, or encode them in a link and send that link to someone else.

Information Processed Automatically When You Visit

Like any website, the site infrastructure that serves pages may process standard request metadata such as IP address, requested path, browser type, and timestamp in order to deliver files, cache responses, and protect the service from abuse. We do not use those operational requests to build advertising profiles or body-measurement dossiers, but some level of basic network processing is inherent in serving a website at all.

The current front-end codebase does not include Google Analytics, Google Tag Manager, Meta Pixel, TikTok Pixel, ad scripts, or first-party cookie-consent logic. In practical terms, that means the site is not currently instrumented to send pageview analytics events or advertising beacons from its own page code. If that changes later, we will update this policy to describe the change rather than hiding it in a silent deploy.

The site does load external web fonts from Google Fonts. When your browser requests those font files, it makes a connection to Google infrastructure and Google may process technical request information under Google’s own privacy terms. We use those fonts to render the site consistently, but we do not control Google’s handling of the request once your browser connects to them.

Information We Do Not Intentionally Collect

The site is built specifically to avoid collecting several categories of information that would be easy to overreach on in this niche. We do not intentionally collect measurement entries on our own servers through the calculator UI. We do not maintain user accounts. We do not ask for payment information. We do not run a newsletter signup tied to body-shape data. We do not run analytics scripts in the current code. We do not embed advertising networks in the current code. And we do not try to infer a long-term profile of your body measurements across sessions on our own backend.

• Body measurements entered into the calculators are not sent to our server by default.
• Body-type results are not stored in an account profile because there is no account system.
• No first-party analytics or ad tags are present in the current site code.
• No payment data is requested because the site does not sell subscriptions or products.

How We Use Your Information

We use correspondence data to answer the question you asked, review correction requests, handle privacy concerns, or evaluate collaboration inquiries. If you send a correction report, we may use the content of that report to verify and improve the relevant page. If you write to us about a privacy issue, we may need to refer to the message in order to understand or document the request.

We use browser-local data, where it exists, to improve usability for you rather than for us. For example, the main calculator can preserve recent unit and measurement choices in localStorage. The waist-to-hip ratio calculator can preserve its last-used values locally. Measurement guides can save draft inputs, unit preferences, or tracking entries in the same browser. Those storage mechanisms exist so you do not lose context after a refresh; they are not used to transmit data back to us.

We may also use operational request data handled by hosting infrastructure to keep the site available and defend it from abuse. That is different from using analytics to understand individual behavior or using ad tech to target users. The current codebase is intentionally minimal on both of those fronts.

Calculator Data - How It Works

This section matters because it addresses the most common privacy question directly: what happens when you type measurements into the tools? Under the current implementation, the answer is that the calculations are performed by JavaScript running in your browser. The entered values are read by the page, used to compute ratios and category outputs, and shown back to you in the same browsing session.

Several tools also offer convenience features that store state locally. The main body-type calculator can store gender, unit, optional high-hip preference, and current values in browser-local storage. The waist-to-hip ratio calculator can store gender, unit, and the most recent waist and hip values in browser-local storage. The short and long measurement guides can store draft measurement entries and unit settings. The full-body measurement guide also stores locally created tracking sessions and draft chart rows if you use its tracker.

In addition to local storage, some tools can build shareable URLs containing result information. The main calculator can encode result type and measurement values into the URL hash or query string, depending on configuration. The waist-to-hip ratio calculator can place result values in the URL hash. That is useful if you want to copy or bookmark a result, but it has an obvious privacy implication: anyone who sees the full URL may see the values encoded in it. If you do not want measurements visible in a share link, do not share that URL and clear it from the address bar before copying the page location.

Because the tools are browser-based, you can often inspect this behavior yourself. Browser developer tools can show local storage keys, and the address bar can show whether a result hash is present. We consider that inspectability a feature, not a problem.

Cookies and Similar Technologies

Cookies Set by the Current Site Code

The current front-end codebase does not intentionally set analytics, advertising, or marketing cookies. There is also no cookie-consent banner implemented in the current site code because the site is not currently shipping a first-party analytics or ad stack that depends on one.

That does not mean your browser will never store anything. Browser caches, connection state, and provider-controlled mechanisms can still exist as part of ordinary web delivery. But those are different from a site actively writing tracking cookies for measurement-based profiling.

Local Browser Storage

Several parts of the site use window.localStorage. Local storage is not a cookie; it is a browser-provided mechanism that stores key-value data on your device for a specific origin. The site uses it to preserve drafts, units, and optional tracker data between reloads. The important privacy point is that this storage remains on your device unless you deliberately share the information another way.

You can usually clear this data through your browser settings or developer tools. In some features, the site also offers a direct way to overwrite or export the local data. Clearing local storage for the site will typically reset saved drafts and unit preferences.

Third-Party Requests

We load web fonts from Google Fonts. Your browser therefore contacts Google-hosted resources when fetching those font assets. That request is governed by Google’s policies and infrastructure, not just by ours. If you are particularly sensitive to third-party requests, you should be aware that loading the site with default settings may involve those font requests.

Third-Party Services

Based on the current site code, the most visible third-party service in active use is Google Fonts. The site also necessarily depends on hosting and delivery infrastructure to serve static files, but provider details can change over time and are not hard-coded into the public front-end pages in the same way a font request is. We therefore avoid claiming a permanent hosting vendor in this policy unless the site implementation makes that relationship explicit.

The contact page includes a browser-side fallback that can open your local mail application with a drafted message. In the current repository state, no third-party hosted form endpoint is configured by default. If we later enable a hosted form processor, this policy will be updated to identify that processor and describe the data flow.

We do not currently state that we use analytics providers, advertising networks, or social-media pixels because the current codebase does not include them. If they are ever added, this page will be revised.

Data Retention

Data retention depends on the category of information involved. Because the site keeps so much of its state in the browser, much of the relevant retention is under your control rather than ours.

If you email us and want that correspondence deleted, ask. If you want locally stored measurement data removed, the fastest route is usually clearing local storage or site data in your browser. If you are concerned about a shareable URL containing measurement information, clear or replace the URL and remove it from bookmarks or copied notes where possible.

Your Rights and Choices

GDPR and UK GDPR Rights

If data protection law applies to you, you may have rights such as access, correction, deletion, restriction, objection, and data portability in relation to personal data we actually control. In a site like this, that generally means correspondence data and any information we can identify in relation to a direct contact you initiated, not the measurement values that stay only in your browser.

To exercise a privacy right, email contact@aigotowork.work with enough detail for us to understand what data or interaction you are referring to. We may need to ask for clarifying information so we can identify the correct correspondence or explain what is under our control versus what remains only on your device.

California Privacy Rights

California residents may have rights regarding access to and deletion of personal information a business collects about them, subject to applicable limits and exceptions. We do not currently sell personal information, and the current codebase does not include a targeted advertising stack. As with GDPR-style requests, the most relevant category of data we control is usually your direct correspondence with us.

All Users

Regardless of location, you can make several privacy choices immediately without asking us for anything. You can avoid sharing generated result URLs. You can clear local storage and site data in your browser. You can choose not to email personal details that are unnecessary for your question. And you can contact us whenever a page seems unclear about what it stores or exposes.

Privacy on a browser-based tool is partly about what the operator does and partly about what the user chooses to share. We are responsible for the former, and this policy tries to give you enough clarity to handle the latter with intention.

Children's Privacy

The site is intended as a general informational resource and is not directed to children. We do not knowingly seek personal information from children through the site. If you believe a child has sent us personal information directly by email, contact us and we will review the request and remove the message where appropriate.

Data Security

We try to reduce risk primarily by limiting what the site collects in the first place. Front-end-only calculation, no account system, and no current analytics or advertising stack all reduce the amount of data that can be exposed through a breach of an application database because that database largely does not exist here.

That said, no website can promise perfect security. Email is not a magic privacy channel, and browser data remains subject to the security of your device, your browser, and the providers involved in serving the site. If a message is especially sensitive, think carefully before sending unnecessary personal details.

Changes to This Policy

We may update this policy as the site changes. The most likely triggers would be a change in storage behavior, a change in third-party services, the addition of analytics or advertising technology, or a significant shift in how the contact form is processed. When we update the policy, we will revise the “Last updated” date at the top of the page and replace outdated statements rather than leaving them in place as dead text.

Contact Us

If you have a privacy question, want help understanding what a page stores locally, or want to request deletion of correspondence you sent us, email contact@aigotowork.work. You may also use the backup address midoriko053@gmail.com if needed.

Please include enough detail for us to identify the interaction you are asking about. For example: the page you used, whether you are asking about local storage, a shared URL, or email correspondence, and the action you want us to take.