Privacy FAQ
Does Body Visualizer store your data?
You can create the core 3D preview without uploading a photo or creating an account.
Content reviewed: August 3, 2026
Measurements in the visualizer
The interactive model uses the values entered in your browser to update the preview. The tool uses numbers rather than photographs, webcam images, or biometric scans. Height, weight, waist, hips, chest, and optional goals update the browser preview.
Optional AI analysis
If you request AI analysis, the displayed measurements are sent to the analysis endpoint to generate the response. The core preview uses current-session values and does not create a personal measurement profile. When optional AI analysis is requested, displayed measurements are sent to the analysis endpoint; review the privacy policy for current handling details.
Stay in control
Avoid entering identifying details and close or reset the tool when you finish on a shared device. Use only necessary measurements, avoid names and medical details, reset or close shared devices, and decide whether optional analysis is appropriate before sending values.
What the core preview needs
The basic visualizer works from numeric inputs and does not require a photograph, webcam, or personal biography.
Enter measurements, not identity details
Height, weight, waist, hips, chest, and optional goal values are enough for the measurement-based preview. A name, address, phone number, employer, medical history, and free-form personal story are not needed. Keeping unnecessary identifiers out of any input is a practical privacy boundary. The absence of a photo requirement also means the core task can be completed without providing an image of the user's face, room, clothing, or surroundings.
The browser session is part of the privacy context
Values displayed in the interface can remain visible to someone who uses the same open browser or device. Before leaving a shared computer, reset the controls when available, close the page, and check whether the browser restores previous tabs. Screen captures, copied text, autofill, browser extensions, and device-level monitoring are separate from the site's own features. A private session reduces some local traces but is not a guarantee against operating-system, network, or extension logging.
Separate the preview from optional analysis
Updating the on-screen model and requesting an AI response are different actions with different data flows.
The core interaction updates the displayed model
Numeric controls update the preview as values change. This interaction should be understood separately from any button that explicitly requests analysis. The privacy explanation describes the core preview as using current-session values rather than creating a personal measurement profile. That statement does not promise how every browser, extension, network, or hosting log behaves, so the current privacy policy remains the source for operational details beyond the page's visible behavior.
Optional analysis sends displayed measurements
When a user deliberately requests the optional AI analysis, the displayed measurements are sent to the analysis endpoint so a response can be generated. Do not include extra identifiers or medical details that the feature does not request. Before submitting, review the values on screen, decide whether the response is needed, and consult the current privacy policy for handling details. Skipping optional analysis leaves the numeric preview available for the basic visualization task.
Control what is shared and retained locally
Data minimization starts with entering only the fields needed for the selected feature and clearing what remains visible afterward.
Use the minimum necessary values
Optional goals can be omitted when they are not part of the comparison. Avoid placing identifying information into measurement fields or any free-text area. If a value is not needed to produce the desired view, leaving it out reduces the information involved. This principle does not require guessing about unseen systems; it is a direct choice available before submission. Review each field for unit mistakes as well, because correcting an accidental entry after sending it cannot undo the original request.
Manage shared-device exposure
On a shared phone, tablet, or computer, another person may see the open page, browser history, recent tabs, clipboard, downloaded files, or screenshots. Reset the interface, remove copied results, and close the session according to the controls of that device. If the browser synchronizes history or tabs to another account, local closing may not remove synchronized records. Device and browser settings therefore matter alongside the site's privacy policy when evaluating the practical privacy of a session.
Read policy language at the time of use
A FAQ can summarize the visible workflow, while the privacy policy provides the current formal description of handling practices.
Use the policy for current operational details
Services, hosting arrangements, retention practices, and legal requirements can change. For that reason, this page links to the current privacy policy rather than making permanent promises about every technical log or service provider. Check the policy when the detail affects a decision, especially before optional analysis. Note the effective or updated date if comparing an older explanation with the present service. A screenshot or remembered statement may no longer describe the current version.
Distinguish site controls from third parties
Browser extensions, workplace or school device administration, internet providers, and linked external sites may operate under their own rules. Following a reference link leaves the Body Visualizer page and brings the destination's policy into scope. The site cannot clear records created independently by a browser account or managed device. A privacy decision should therefore consider the page action, the device, the browser profile, and any third party intentionally opened during the session.
Respond to mistakes or privacy concerns
If an unintended value was entered or submitted, stop further sharing and use the published contact and policy routes for the next step.
Limit additional exposure
Do not repeat an optional request merely to check whether the first one worked if that would send the same values again. Close or reset the interface, record only the information needed to explain the issue, and avoid posting measurements publicly while asking for help. The contact route can be used for a specific correction or privacy question. Include the relevant page and approximate time, but omit unrelated identity or health details unless they are genuinely required to resolve the request.
Use proportionate privacy expectations
Numeric measurements can still feel sensitive even when they are not accompanied by a photograph or name. Treat that sensitivity seriously without assuming facts the interface cannot prove. The core preview, optional analysis, local browser state, and external links are separate parts of the workflow. Reviewing each part leads to a clearer choice than a single broad claim that data is either completely private or inevitably exposed. When uncertainty matters, skip the optional feature and consult the policy or contact route first.
Read the Body Visualizer privacy policy
Use the preview with deliberate privacy choices
Start with the core numeric preview, share no identifiers, and use optional analysis only when you want it.
Privacy questions and related guides
Does Body Visualizer store my measurements?
The core preview uses current-session values and does not save them as a personal profile.
Do I need to upload a body photo?
No; the preview is based on numeric measurements.
What happens during optional AI analysis?
Displayed measurements are sent to the analysis endpoint to generate the requested response.
How can I use it more privately?
Avoid identifiers, skip optional analysis if unwanted, and reset or close the tool on shared devices.