Visualize TechnologiesVisualize Technologies

Privacy Policy

Last updated: October 28, 2026

Also on this site

Introduction

Visualize Technologies LLC, a Colorado limited liability company doing business as VZN ("Visualize Technologies," "we," "our," or "us"), is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application and website (collectively, the "Service").

By using the Service, you agree to the collection and use of information in accordance with this policy. Where the law or this policy calls for your consent, such as for biometric and consumer health data, we ask for it separately and don't treat using the Service as consent.

Biometric Data Disclosure and Consent

BIOMETRIC INFORMATION NOTICE

The Service collects body scan data and body measurements generated from device sensors (including LiDAR), photos taken during a scan (including photos in which the scanned person's face is visible), and face data derived from those photos: from app version 1.2, points around the eyes and other face data the iPhone records; until October 23, 2026, also facial landmarks and face geometry our servers derived (see "Face Photos and Facial Landmarks"). Such information may constitute "biometric information" or "biometric identifiers" under certain state laws, including the Illinois Biometric Information Privacy Act (BIPA), the Texas Capture or Use of Biometric Identifier Act, the Washington Biometric Privacy Law, the Colorado Privacy Act (biometric amendments effective July 2025), and the New York SHIELD Act.

This biometric data is used for two purposes only: to generate body measurements, 3D visualizations (including the face on the 3D model), transformation predictions, and related fitness or wellness insights for the person scanned and the account holder; and, as described in "Testing and Improving Our Software", to test and improve our own software, including training our own models, inside our company only. We train models on a scan only if the person scanned has agreed. Biometric data is never used to identify or recognize anyone, and faces are never compared with one another. See "Face Photos and Facial Landmarks" below for how face photos are handled.

Consent. From app version 1.2, before anyone is scanned for the first time, the app shows the person being scanned this notice, a summary of the retention policy below and how we use scans, and asks for their written consent: they confirm their name and tap Agree. They choose separately whether their scans may also be used for testing and training; saying no doesn't change the Service. A parent or legal guardian gives consent for a child under 18, and a child aged 13 to 17 is also asked to agree. When a trainer, a gym or a family member scans you, you give consent yourself, on the scanning phone; they can't give it for you. We record what was agreed, by whom and when, and we ask again if this notice changes in a way that matters.

Scans made with app versions before 1.2 were made without this screen. From version 1.2, each person is asked for consent at their next scan, and that consent covers their earlier scans. Until they agree, we use their earlier scans only to provide the Service to them (including fixing problems with their own scans), never to test or train our software.

Disclosure. We never sell, rent, lease or trade biometric data, and never use it for advertising. We disclose it only: to the people the person scanned chooses, and to the account holder who scanned them or a trainer they pair with; to the service providers that store and process it for us under contract (Amazon Web Services); when the law requires it, for example to answer a valid court order; or, with the consent given on the consent screen, to a company that acquires our business, which must keep following this policy. We never share it with another company for testing or training.

Biometric data is kept only for these purposes and on the schedule in the retention policy below.

Biometric Data Retention and Destruction Policy

RETENTION AND DESTRUCTION POLICY (Illinois BIPA, Colorado Privacy Act and other biometric laws)

What it covers. Every file of a body scan (the photos, including the face photos and the face data, the 3D model, the LiDAR depth and pose data, and the person outlines) and the measurements and estimates made from it, wherever we keep them: in the account, in our database backups, and in our test and training sets. We treat the whole scan as biometric data, even where a law might not.

Purposes. We keep biometric data only to provide the Service and, if the person scanned agreed, for the testing and training described in "Testing and Improving Our Software". At least once a year we review whether we still need it for these purposes.

When we destroy it. Biometric data is permanently destroyed at the earliest of these:

  • when the scan, or the account it is in, is deleted;
  • within 30 days after the person scanned asks us to delete it, including a scan someone else took of them;
  • 24 months after the person scanned last interacted with VZN, for example by using their own VZN account or being scanned again (this is shorter than the three years Illinois allows, to meet Colorado law);
  • 45 days after we decide, in our yearly review or otherwise, that we no longer need it for these purposes.

Deleting your account deletes your scans, including earlier (backup) versions of their files, and the scans filed under a phone that is linked only to your account. Deleted records are removed from our database backups within 35 days.

Test and training copies. When you delete a scan or your account, or withdraw your consent to testing and training, we stop using those scans for testing and training within 15 days, and we delete their copies in our test and training sets, on our servers and on our own computers, within 30 days. A test or training copy is never kept longer than the scan it came from. Values we learn for one person, such as how their own predictions compared with their later scans, are deleted with their account. A model we have already trained doesn't store the scans it learned from: it stores numbers adjusted using many scans together, and it can't be used to look up your scan or photos. We keep using models trained before your deletion and don't retrain them, but no model trained after that uses your scans.

Deleting your account does not delete:

  • Copies of your scans that someone else accepted. When you send a scan to another VZN user and they accept it, their copy belongs to them.
  • Scans a trainer took of you. They are part of that trainer's records.

If you are the person in such a copy or scan and want it deleted, ask the trainer, or email vtprivacy@visualizetechnologies.com, and we will delete it within 30 days and tell the account holder. Either way, these copies follow the 24-month limit above.

Legal exceptions. We keep data longer only when the law requires it: content reported to the National Center for Missing & Exploited Children is preserved for at least 90 days (see our Terms), and data covered by a court order or a legal hold is kept until that ends. We also keep a record of the consents given (who agreed, to what and when, but no scan images or face data) for 5 years after the scans it covers are deleted, to show that we had consent.

How we destroy it. We delete every stored copy and earlier version from our servers, our database backups, our test and training sets and our own computers, and we tell our service providers to delete theirs.

If there is a security incident. If we learn that biometric data may have been accessed or taken without authorization, we act at once to stop it and find out what happened and whose data was affected. We notify the people affected, and the regulators the law requires, without unreasonable delay: within 30 days after we determine that a breach occurred for Colorado residents, within 60 days under the FTC Health Breach Notification Rule, and sooner where another law requires it.

This policy is publicly available in compliance with 740 ILCS 14/15(a) and Colorado Revised Statutes § 6-1-1314. It was last reviewed on October 28, 2026.

Face Photos and Facial Landmarks

Body scans capture the scanned person's face with the same camera as the rest of the body; there is no separate face photo step. The face also appears in some of the full-body photos and in the 3D model's texture. During the walk-around, the iPhone's built-in face detection looks for the face in the camera images, and the app keeps up to five photos in which the face is visible (none if no face is found), along with where the face is, which way it is turned and how clear it is in those photos and in other camera images it considered. This happens automatically in every body scan.

From app version 1.2: on iOS 26 or later, the app can also take full-resolution photos silently during the walk-around and keep close-ups cut from them: of the head and hair from several sides, of the hands, and of the whole body, plus up to four more close-ups of the face taken when the person faces the camera. For each of these photos, Apple's built-in Vision software on the iPhone records where the face is and how it is angled (turned, tilted up or down, and tilted sideways), points around each eye, the positions of the pupils, how open each eye is and a photo-quality score, and makes an outline of the person. The close-ups, the face data and the outlines are uploaded with the scan (see "Data Processing" below).

On our servers: today, no software on our servers looks for facial landmarks, no AI model retouches the face, and the servers don't rebuild the 3D shape of the face; the face on your 3D model comes from the model your iPhone builds. For scans from app version 1.2, our servers can use one face close-up and the face data the iPhone recorded to repaint the eyes on the 3D model, and the person outlines to correct the shape of the top of the head. This uses ordinary image-processing software, not AI models.

Scans processed until October 23, 2026 also went through steps we have since removed: software on our servers found facial landmarks (points such as the corners of the eyes and mouth) to pick the clearest face photo and check whether the eyes were open; an AI face-restoration model could retouch that photo, which then replaced the original, and retouched the face in the 3D model's texture; and the servers tried to rebuild the 3D shape of the face. Those landmarks were not kept, but a retouched photo or face texture made then stays with the scan.

  • Not kept: points or measurements of the face that our servers work out while processing a scan. They exist only while the scan is processed.
  • Kept with the scan: the face photos; the face's position, angle and clarity in the camera images; the face as part of the 3D model; and, from app version 1.2, the close-ups, the face data the iPhone records and the person outlines. They follow the retention policy above. A copy of a scan (one you send that someone accepts, or one saved to your account when a pairing ends) includes its face photos.
  • Testing and training: these may be used to test our own software and, only with the consent of the person scanned, to train our own models, as described in "Testing and Improving Our Software".
  • Never: faces are never used to identify or recognize anyone or compared with other people's faces, and face photos and face data are never sent to any company outside Amazon Web Services, where our servers run. (The 3D model, face included, is shown to the people you share a scan with.)

Information We Collect

Personal Information

  • Email address (when you create an account)
  • Name (optional, for display purposes)
  • Apple ID information (if you use Sign in with Apple)

Body and Health Data

  • 3D body scans: the 3D model and measurements (chest, waist, hips, etc.), and the photos, LiDAR depth data and pose data taken during the scan, including up to five photos in which the face is visible and, from app version 1.2, close-ups of the head, hands and body with face data the iPhone records (see "Face Photos and Facial Landmarks")
  • Height and weight information you provide
  • Ethnicity, as set in a profile (in the app: ☰ → Profile), used to adjust body composition and calorie estimates
  • Body composition estimates
  • Fitness goals and preferences
  • Health & Safety Profile answers you or your trainer enter (in the app: ☰ → Workouts → ⋯ → Health & Safety Profile): the seven pre-exercise health questions (based on the PAR-Q+), pregnancy status and due date, whether you take beta-blockers, injuries, and exercises to avoid
  • Food allergies, as entered in a profile (Dietary Preferences) or chosen as filters when you search recipes and foods
  • Apple Health data (only if you connect Apple Health, and only for your own profile): steps, active energy, workouts, sleep, resting heart rate, weight, body fat, height, date of birth and biological sex
  • Food and workout logs you record in the app, including the food photos and spoken food names you use to log a meal

Trainer and Sharing Data

  • Messages, notes and shared-profile details exchanged with a trainer you pair with
  • Scans you send to other VZN users, and the share links you create (their settings and how many times they have been viewed)

Support Data

  • Your support chat conversations, and the account details sent with them (see "Support Chat")
  • Emails you send us

Usage Data

  • Device information (model, operating system)
  • App usage patterns and feature interactions
  • Diagnostic logs, crash and performance reports, and failed-scan reports (see "Diagnostic Logs")

How We Use Your Information

  • To provide and maintain our Service
  • To process your 3D body scans and generate measurements
  • To create body transformation predictions
  • To sync your data across devices
  • To deliver scans, plans, logs, messages and notes between you and a trainer you pair with
  • To show a scan to the people you choose to share it with, including through share links you create
  • To test and improve our own software, and, only with the consent of the person scanned, to train our own models on scans (see "Testing and Improving Our Software")
  • To find and fix crashes and failed scans (see "Diagnostic Logs")
  • To communicate with you about your account
  • To provide customer support, including through our AI support assistant (see "Support Chat")

Testing and Improving Our Software

We use scans to test and improve our own software, including to train our own models. For example, we run new versions of our scan processing on earlier scans to check that they work and to compare the results, and we may train models that make the 3D model, its texture (including the face), the measurements or the predictions more accurate.

  • What we may use: the files uploaded with a scan (the 3D model, the photos, including the photos in which the face is visible, the face data the iPhone records, the LiDAR depth data, the person outlines and the pose data) and the results our servers make from them, such as measurements. We don't put names or email addresses in training sets, and we never use Apple Health data to train models.
  • Where: only inside Visualize Technologies, on our own servers at Amazon Web Services and on our own computers.
  • Never: scans are never sold or licensed to anyone, never shared with another company for testing or training, never used to identify or recognize anyone, and never used for advertising.
  • Your choice: from app version 1.2, the app's consent screen asks the person scanned whether their scans may be used for testing and training (see "Biometric Data Disclosure and Consent"). We train models on a scan only if they said yes, and if they said no, we leave their scans out of testing too. Saying no doesn't change the Service.
  • Scans made before that consent screen: until the person scanned agrees in version 1.2 or later, we use them only to provide the Service to them (including fixing problems with their own scans), not to test or train our software.
  • Children: we never put scans of anyone under 18 in our test or training sets, even with a parent's consent. We look at a child's scan only to fix a problem with that scan.
  • Leaving your scans out: you can withdraw your consent at any time in the app (from version 1.2, in the privacy choices in Settings), or email vtprivacy@visualizetechnologies.com about any scan, including earlier ones. We stop using your scans for testing and training within 15 days and remove them from our test and training sets within 30 days. This doesn't affect the rest of the Service.

What happens to these copies when you delete a scan or your account is described under "Biometric Data Retention and Destruction Policy".

Scanning Other People and Children

Trainers, gyms and family members can scan other people with VZN. When you scan someone else:

  • The person scanned must agree themselves. From app version 1.2, the app asks them for consent before their first scan, on your phone. You can't agree for another adult, and you must not scan anyone who says no or who hasn't agreed.
  • They have rights over their scans. The person scanned has the same rights over scans of them as an account holder (see "Your Rights" and our Consumer Health Data Privacy Policy), and can ask us directly to see or delete them, even if they have no VZN account.
  • Trainers and gyms have their own duties. As businesses, they are responsible for the privacy laws that apply to them where they work, including any notice or consent rules for collecting biometric data. Our consent screen is built to help, and our Terms of Service explain these duties.

Children.

  • Accounts are for adults 18 and older. An adult may scan a child under 18 only if they are the child's parent or legal guardian, or the parent or guardian gives consent on the consent screen. A child aged 13 to 17 is also asked to agree, and isn't scanned if they say no.
  • We use a child's scans only to provide the Service to the family or trainer who made them. We never use them to test or train our software or for any other purpose in this policy.
  • A parent or guardian can see, export or delete their child's scans at any time, in the app or by emailing vtprivacy@visualizetechnologies.com.

Data Storage and Security

Your data is stored securely using Amazon Web Services (AWS):

  • In Transit: All data transmitted between your device and our servers is encrypted with TLS (HTTPS)
  • At Rest: Data stored on our servers is encrypted using AES-256 encryption
  • Authentication: Secure token-based authentication protects your account

3D body scans and measurements are stored in encrypted cloud storage. Server processing runs on AWS: the processing servers accept no incoming connections from the internet, and access to stored scan files is logged.

Data Processing

When you capture a body scan:

  1. On your iPhone, the app captures the scan with the camera and LiDAR sensor and builds a first 3D model.
  2. It keeps a set of photos from the scan: eight full-body photos (one every 45 degrees), up to five in which the face is visible, and up to three of the feet. From app version 1.2, it can also keep close-ups of the head, hair, hands and body, with face data and person outlines (see "Face Photos and Facial Landmarks").
  3. If you are signed in, the app uploads the 3D model, those photos, the LiDAR depth data, the outline of the person in the photos, pose data (from app version 1.2, also the camera's position for each LiDAR frame, the body joint positions the iPhone detects, and the measurements it takes from the LiDAR data), and the scanned person's profile (such as name, height, weight, sex, age and goals).
  4. Our AWS servers refine the 3D model and its texture (see "Face Photos and Facial Landmarks" for the face), and produce the measurements, predictions and body composition estimates.
  5. The results are sent back to your device over an encrypted connection.

Access Controls

Access to your data is managed as follows:

  • Only you can access your scans and measurements through the app, unless you pair with a trainer or share a scan (see "Trainer Pairing and Companion Access" and "Sharing Scans and Share Links" below)
  • Trainers can see only the data listed under "What Your Trainer Sees" below, and only after you pair with them
  • Authorized personnel may access data stored on our servers, and copy scans to our own computers, for technical support, debugging, testing and improving our software (see "Testing and Improving Our Software"), or to respond to your requests
  • Access to stored scan files on our servers is logged
  • Third parties receive your data only as described in "Data Sharing" and "Third-Party Services" below

Data Sharing

We do not sell your personal information. We may share data only in these circumstances:

  • With your consent: When you choose to share scans with trainers or gyms, pair with a trainer, send a scan to another VZN user, or create a share link (see the next two sections)
  • Service providers: AWS for hosting and processing (including the AI models we run through Amazon Bedrock), Apple for sign-in, subscriptions and speech recognition, Authorize.net for gym plan payments, Spoonacular for recipe and food search, Open Food Facts for barcode lookups, GitHub, which holds our older crash reports, and Google Workspace for our email (see "Third-Party Services" below)
  • Legal requirements: When required by law or to protect our rights
  • Business transfers: If Visualize Technologies is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or part of its business or assets, personal information, including scans and the models trained on them, may be transferred to the other company as part of that deal. Before a deal, we share scans, photos or health data with a company considering it only with the consent of the person scanned. A new owner must keep using personal information as this policy describes; we will tell you before it becomes subject to a different privacy policy, and ask for your consent where the law requires it, for example before biometric or consumer health data is used for a new purpose.

Trainer Pairing and Companion Access

You can pair with a personal trainer, or a trainer at your gym, by entering the pairing code they give you in the app. A trainer sees nothing from your account unless you pair with them, and our servers check that your pairing is active before sharing anything listed below with them.

A code you redeem on our website (visualizetechnologies.com/redeem) can also pair you. If the code came from a trainer, redeeming it connects you with that trainer as described in this section: they see the meals and workouts you log and can message you. The website shows you the trainer's name and asks you to confirm before it connects you.

If your trainer has an active VZN trainer or gym plan, you can use the VZN app free while you are paired ("companion access").

What Your Trainer Sees

While a pairing is active, your trainer sees only:

  • Your logged days: the meals, water and workouts you log in the app, and your workout stats.
  • Your shared profile: your name and basic stats (height, weight, gender and birth date), which either of you can update.
  • Notes and chat: the notes you write for them, and the chat messages you send each other.
  • The scans they take of you.

Your trainer never sees:

  • Your grocery lists, favorite foods or preferences
  • Your journal
  • Other profiles on your account, such as family members
  • Your own calorie and macro targets, your saved diet profile, or any values derived from Apple Health

Raw Apple Health readings are never shared with your trainer; values you choose to save to your profile, like your weight, can appear in the profile you share with them (see "Apple Health Data" below).

What You See

  • Scans your trainer takes of you are delivered to your gallery automatically, with their measurements.
  • Your trainer's workout plan and nutrition targets for you, read-only.
  • Chat messages you and your trainer send each other.
  • Notes your trainer chooses to share with you. Notes your trainer keeps private are never shown to you.

If you are the trainer, the same applies from your side: your paired clients see the scans you take of them, the plan and targets you set, and the notes you share with them, but never your private notes.

When a Pairing Ends

Either of you can end a pairing at any time. When a pairing ends, or if your trainer deletes their account, independent copies of the scans your trainer took of you and delivered to your account are saved to your account. The copies belong to you: you can keep viewing and downloading them, and they are deleted if you delete them or your account.

Once a pairing ends, our servers stop sharing your logged days, shared profile and notes with that trainer, and share links to the scans that trainer took of you stop working, whoever created them. Your chat history with that trainer stays readable to both of you. Your trainer keeps their own records, such as the scans they took of you, unless they delete them; to have those deleted, ask your trainer, or email vtprivacy@visualizetechnologies.com.

Sharing Scans and Share Links

Sending a Scan to Another VZN User

You can send a scan of yourself to another VZN account by entering their email address. Only scans of you, the account holder, can be sent this way, never a scan of a client or of a family member on your account. The person you send it to sees your name (or "A VZN user"), never your email address, and can accept or decline. If they accept, they get their own independent copy of the scan in their account. That copy is theirs: it stays in their account even if you later delete your original or your account.

Share Links

You can create a web link to a scan you took, or to a scan a trainer took of you. A trainer can create one for a scan they took of you only while you are paired. A copy of a scan someone sent you can't be shared as a link. Anyone who has a link can open it in a web browser, without the VZN app or an account.

  • What the page shows: the 3D model (viewable in the browser, and in augmented reality on iPhone), a preview image, the sender's first name and the date the scan was captured. Body measurements (body dimensions such as height, chest and waist) appear only if the sender chooses to include them. Weight and body fat are never included, and the page never shows a user ID, email address or scan ID.
  • How long it lasts: the sender chooses 1 to 30 days (7 by default). The person who created the link, the scan's owner and the person scanned can each turn it off at any time. A link also stops working if the scan is deleted. Links to scans a trainer took of you stop working when the pairing ends and when you delete your account, whoever created them.
  • Someone else's scan: before anyone creates a link to a scan of another person, such as a trainer sharing a client's scan, the app asks them to share it only if that person has agreed.
  • Not listed or indexed: share-link pages aren't linked from anywhere on our site, and they tell search engines not to index them.
  • How links are stored: our database stores only a hashed form of each link; like any web address, the full link can appear in your browser history and our hosting logs. The files a link shows are separate copies made for that link; they are deleted when the link is turned off, and removed automatically after about a month in any case. The page loads them through temporary addresses that expire after 15 minutes.
  • Views: we count how many times each link is opened, and a daily view limit applies. The people who can turn a link off can see its view count.
  • Account deletion: deleting your account turns off the share links you created, links to your scans, and links to scans a trainer took of you.

Anyone who has a link can view, save or pass on what it shows while it works, so share links only with people you trust.

Third-Party Services

The Service relies on the following third-party providers to operate. These providers may process limited data as necessary to deliver their services:

  • Amazon Web Services (AWS): Cloud hosting, storage, server-side processing of scans and data, and the email and notification services our servers use
  • Anthropic's Claude, through Amazon Bedrock: We run Anthropic's Claude AI models through Amazon Bedrock, part of AWS, for: the support chat (see "Support Chat"); identifying the food in a photo you take to log a meal (the photo only, without your name or account details); and suggesting causes of crashes and failed scans (see "Diagnostic Logs"). Scan photos, face photos and 3D models are not sent to these models. (Until October 14, 2026, our servers also sent gray, untextured pictures of each 3D model, never photos, to check it for defects.)
  • Apple: Sign in with Apple, App Store subscriptions, Apple Health (HealthKit), push notifications, App Attest (which checks that requests come from the genuine app), the crash and performance reports iOS provides, and speech recognition when you use voice input (Apple may process the audio on its servers)
  • Authorize.net: Card payments for gym plans bought on our website. Your card details go from your browser straight to Authorize.net; our servers receive only a one-time payment token, never your full card number, and pass it to Authorize.net with the billing address and the signer's email address.
  • Spoonacular: Recipe and food search. In app version 1.1 and later, the app sends these requests to our servers, which pass them on to Spoonacular; we don't store your searches. Some earlier versions call Spoonacular directly from the app, so Spoonacular also sees your device's IP address, as any website would. In every version, the app loads recipe and food pictures straight from Spoonacular's image servers, which see your device's IP address, and a recipe you import from a link can load its picture from that recipe's website. Spoonacular receives your searches and filters (such as diet type, cuisine, calories and protein), food names you say or type when logging a meal, recipe links you paste, and a meal photo if our own analysis of it fails. Your food allergies, and the foods you exclude from recipes, are sent only if you allow it: the app asks the first time a recipe search has allergies to filter for, and if you don't allow it, it filters the recipes on your iPhone instead. Spoonacular does not receive your name, email address or account ID.
  • Open Food Facts: When you scan a product barcode, the app looks it up in Open Food Facts, a public food database, sending only the barcode number.
  • Instacart: When you choose to shop your grocery list or a recipe on Instacart, the app copies the items for you and opens Instacart; we don't send Instacart your list or anything else. You shop and check out in your own Instacart account; we never see your Instacart login or payment details.
  • GitHub: Until spring 2026, we tracked crash and failed-scan reports as issues in our private GitHub repository. New reports no longer go there. The issues already there contain user IDs and device and crash details, but not names or email addresses (see "Diagnostic Logs").
  • Google Workspace: Hosts our email, including emails you send us and our internal alerts about crashes and failed scans, which include your name, email address and user ID.
  • Google and Clearbit (website only): a few pages of our website load fonts or a 3D viewer from Google's servers, and gym proposal pages can show a gym's logo loaded from Clearbit or Google. Those servers see your IP address and the page that asked, as with any website.

We do not share your personal data with analytics providers, advertising networks, or data brokers.

Affiliate Links

Our website includes a tag from an affiliate network, Impact (impact.com), meant to track affiliate links. Our website's security settings currently stop the tag from loading, so it doesn't run and Impact receives nothing from our website, and our website has no affiliate links. We will update this policy before we turn it on.

Support Chat

The support chat in the app (☰ → Settings & Support → Support Chat) is answered by an AI assistant, Anthropic's Claude, run through Amazon Bedrock on AWS, not by a person. The app asks for your consent before your first message. Its answers can be wrong; to reach a person, email vtsupport@visualizetechnologies.com.

The assistant receives what you type (the conversation so far, up to the last 20 messages) and account basics that help it answer: your user ID and display name, your plan and account status, your scan usage, and your gym organization ID if you have one. When you start a conversation, it also receives your app version, iOS version and device model, and whether the app crashed the last time you used it. It does not receive your email address or anything about the profiles on your account, such as clients. Whatever you type is sent, so don't type health details you don't want to share.

Conversations are stored on our servers and on your iPhone. The server copy is deleted when you delete your account.

Diagnostic Logs

To find and fix problems, the app uploads diagnostic information to our servers automatically. There is currently no setting to turn this off.

  • Activity logs: the app's record of what it did, uploaded shortly after the app opens and when you return to it (at most once every 10 minutes), and when you tap Send Diagnostics in Support Info. A log can include your user ID, the domain of your email address, scan IDs and file names, and your device model, iOS version, app version and memory. Removed on your iPhone before a line is written: health and body values (height, weight, age, body measurements and body fat, heart rate, calories, sex and ethnicity, and anything about allergies, pregnancy, injuries, medications or medical conditions), email addresses (all but the domain), your name and the names of your profiles, trainers and paired clients, and push tokens. Logs uploaded by versions of the app before 1.0.9 can also include your email address, name, the names of profiles on your account, and health and body values. Logs are encrypted on your iPhone before upload, with a key our team can recreate so we can read them when diagnosing a problem.
  • Crash and performance reports: the reports iOS gives the app about crashes, hangs and heavy battery or storage use, and details of errors the app records (the error, where it happened, and the app's recent steps).
  • Failed-scan reports: when a scan fails, the app uploads the error, your device model, iOS and app version, memory in use and available, the app's recent steps, and your user ID (or, if you are signed out, an ID the app makes for your device).
  • Upload status: a list of the scan files waiting to upload (names and sizes).

Who sees them: our team. A failed scan or crash report also creates an alert email to our team, which includes your name, email address, user ID, plan and gym ID with the problem details. The technical details of failed-scan and crash reports (not your name, email address or user ID) are sent to Anthropic's Claude through Amazon Bedrock to suggest a cause. Until spring 2026, these reports also became issues in our private GitHub repository (with user IDs and device and crash details, not names or email addresses), where an automated tool that runs on GitHub's servers could send an issue to Claude through Amazon Bedrock to suggest a fix; new reports no longer go there. Activity logs themselves are never sent to GitHub, to an AI model or by email.

How long they are kept: diagnostic logs and reports, and the GitHub issues and alert emails made from them, currently have no automatic time limit. Deleting your account deletes the logs and reports stored under your account (see "Account Deletion"), but not logs the app uploaded while you were signed out (filed under an ID for your device), the alert emails, or the GitHub issues. To have those deleted, email vtprivacy@visualizetechnologies.com and we will delete them within 30 days.

Apple Health Data

If you connect Apple Health (in the app: Settings → Health Data), the iPhone app reads steps, active energy, workouts, sleep, resting heart rate, weight, body fat, height, date of birth and biological sex. The iPhone app does not write to Apple Health.

The VZN Apple Watch app saves the workouts you record on it to Apple Health, and reads your heart rate and active energy while you record them, to show them live and in your workout summary.

How we use it: to personalize your own calorie and training targets, the Health view on your Apple Watch, and the score shown in progress videos of your own scans (in the Gallery). Apple Health data is used only for your own profile, never for a client's profile, screen, video or Watch view.

Where it is kept:

  • On your iPhone: one summary per day for the last 120 days, in the app's storage. It is not stored in iCloud and is excluded from device backups.
  • On our servers: only if you turn on "Back up daily Health summaries to VZN". The backup holds the same daily summaries (steps, active energy, workouts, resting heart rate, time asleep, weight and body fat). Turning backup off deletes it.
  • In your profile: if you choose to import weight, height, body fat, age or sex from Apple Health, those become profile values and are saved with your account like any value you type in.

Apple Health data is never sold, never used for advertising or marketing, never shared with gyms or other third parties, and never stored in iCloud. Raw Apple Health readings are never shared with your trainer; values you choose to save to your profile, like your weight, can appear in the profile you share with them.

Turning it off and deleting it: to stop the app reading Apple Health, go to iPhone Settings → Privacy & Security → Health → VZN. To delete our copies, open Settings → Health Data in the app: turning off backup deletes the server copy, and "Disconnect Apple Health" deletes both the server copy and the copy on your iPhone. Deleting your account also deletes them.

Consumer Health Data

Our Consumer Health Data Privacy Policy explains what consumer health data we collect (including body scans, measurements, body-composition estimates, Health & Safety answers such as pregnancy status, and Apple Health data), why, where it comes from, who we share it with, and how to use your rights. It is written for Washington's My Health My Data Act (RCW 19.373), Nevada's SB 370 and Connecticut's consumer health data law, and we apply it to everyone.

  • From app version 1.2, we ask the person scanned for consent before collecting their consumer health data, and separately before using it for testing and training and before sharing it with a trainer or gym.
  • We never sell consumer health data.
  • You can withdraw consent, and ask us to delete your consumer health data, at any time. We respond within 45 days.
  • We don't use geofences (virtual boundaries around a place) around health care facilities or anywhere else, and the app doesn't collect your location.

For all users: if there is a breach of your health information, we will notify you within 60 days, as the FTC Health Breach Notification Rule requires, and sooner where a state law requires it.

Your Rights

You have the right to:

  • Access your personal data
  • Export your data in a portable format (JSON, CSV, or both)
  • Request correction of inaccurate data
  • Request deletion of your data
  • Opt out of marketing communications
  • Stop Apple Health access at any time (iPhone Settings → Privacy & Security → Health → VZN) and delete our copies in the app's Settings → Health Data

Data Export

To request a copy of your data, email vtprivacy@visualizetechnologies.com with your User ID (found in Support Info) and preferred format. Data export includes all body scans, 3D models, measurement history, and profile information.

Account Deletion

You can delete your account in the app: open the ☰ menu, tap Account, tap Delete Account at the bottom, then confirm (Continue, then Delete Forever). You can also email vtprivacy@visualizetechnologies.com with subject "Account Deletion Request" and include your User ID and account email; we deactivate the account right away and delete your personal data within 30 days.

Deleting your account deletes your scans, including earlier (backup) versions of their files, and the scans filed under a phone that is linked only to your account. Deleted records are removed from our database backups within 35 days. Copies of your scans in our test and training sets are deleted within 30 days (see "Biometric Data Retention and Destruction Policy").

Deleting your account also deletes the diagnostic logs, crash reports and app-usage records stored under your account. It doesn't delete logs the app uploaded while you were signed out (filed under an ID for your device), or the alert emails and GitHub issues about your failed scans or crashes (see "Diagnostic Logs"). To have those deleted too, email vtprivacy@visualizetechnologies.com. We keep records of your subscription purchases as business records.

Two kinds of copies stay with other people: copies of your scans that someone else accepted are theirs, and scans a trainer took of you are part of that trainer's records. To have a trainer's scans of you deleted, ask the trainer, or email vtprivacy@visualizetechnologies.com.

Deleting your account also turns off the share links you created, links to your scans, and links to scans a trainer took of you. If you are a trainer, your paired clients keep independent copies of the scans you took of them (see "When a Pairing Ends" above).

We respond to requests within 45 days, and usually sooner. See "Your State Privacy Rights" below for who can make a request, how we verify it and how to appeal.

Age Requirement and Children's Privacy

Accounts are only for adults 18 and older. By creating an account, you represent and warrant that you are at least 18 years old. We do not knowingly let anyone under 18 create an account or use the app themselves, and we may suspend or delete an account we find belongs to someone under 18.

An adult may scan a child under 18 only as described in "Scanning Other People and Children": as the child's parent or legal guardian, or with the parent's or guardian's consent on the consent screen. We treat children's data as sensitive data, and we never use children's scans for testing or training.

If you are a parent or guardian and believe your child has given us personal information, or was scanned without your consent, contact us at vtprivacy@visualizetechnologies.com and we will delete it.

Your State Privacy Rights

Many states give their residents privacy rights, including California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah and Virginia; Alabama, Louisiana, Oklahoma and Vermont when their laws take effect; and Washington and Nevada for health data. Some of these laws apply only to larger companies. We offer the rights below to everyone, wherever they live.

Your rights

  • Know and access: confirm whether we process your personal data, and get a copy in a portable format (JSON, CSV or both), with the categories of personal data we have, including what we have worked out about you (such as body-composition estimates and predictions), where it came from, why we use it, and the third parties we have disclosed it to, by name if you ask.
  • Correct inaccurate personal data.
  • Delete your personal data, including scans of you that someone else took.
  • Withdraw consent you gave, for example to testing and training, or to processing your sensitive data.
  • Opt out of the sale of personal data, targeted advertising, and profiling that produces legal or similarly significant effects. We don't do any of these, so there is nothing to switch off, but you can still ask and we will record your choice.
  • Not be treated differently for using these rights.

Sensitive data

Several states treat biometric data, health data, information about pregnancy, racial or ethnic origin, and data about children as sensitive data. We process sensitive data only with consent (from app version 1.2, through the consent screen; for a child, a parent's or guardian's consent) and only for the purposes in this policy. We never sell sensitive data. We don't use personal data to train large language models.

How to make a request

  • Email vtprivacy@visualizetechnologies.com with your request and, if you have an account, your User ID (in the app's Support Info). You can also delete your account in the app. If someone else scanned you, tell us who and roughly when (see "Scanning Other People and Children").
  • Verification: we check that a request comes from the email address on the account. If it doesn't, we ask for the least information we need to confirm who you are, and use it only for that.
  • Authorized agents: someone you authorize can make a request for you where your state's law allows it. They must give us your signed permission or a power of attorney, and we may ask you to confirm your identity directly. A parent or legal guardian can make requests for a child.
  • Timing: we respond within 45 days of receiving your request. If we need more time, we may extend this once by up to 45 more days where the law allows, and we'll tell you why within the first 45 days. Requests are free, up to twice in any 12 months.

How to appeal

If we decline your request, in whole or in part, we'll tell you why. You can appeal by replying to our decision or by emailing vtprivacy@visualizetechnologies.com with the subject "Privacy Appeal". We'll respond in writing within 45 days, explaining what we did and why. If we deny your appeal, you can contact your state Attorney General, and our response will tell you how.

California (CCPA / CPRA)

  • Right to know what personal information is collected, used, and disclosed, and to get a copy
  • Right to delete personal information
  • Right to correct inaccurate personal information
  • Right to opt out of the sale or sharing of personal information (we don't sell or share personal information as the CCPA defines those terms, and haven't in the past 12 months)
  • Right to limit the use of sensitive personal information, including biometric and health data: we treat a request to limit as withdrawing consent to testing and training and to any use beyond providing the Service
  • Right to non-discrimination for exercising privacy rights

See also our Notice at Collection for California residents.

Biometric data

Under the Illinois Biometric Information Privacy Act, Texas's Capture or Use of Biometric Identifier Act, Washington's biometric identifiers law (RCW 19.375), the Colorado Privacy Act's biometric provisions and similar laws, you have the right to:

  • Be told, before biometric data is collected, what is collected, why, and how long it is kept
  • Give or refuse consent. Without it we can't make a scan, because a scan is biometric data, but refusing doesn't affect the rest of the Service
  • Ask what biometric data we have about you, where it came from, why we process it and whom we have disclosed it to
  • Have your biometric data destroyed, on the schedule in our retention policy or sooner if you ask

Global Privacy Control

We treat a Global Privacy Control (GPC) signal as a request to opt out of the sale or sharing of personal information and of targeted advertising. We don't sell or share personal information or use it for targeted advertising, so there is nothing more to switch off.

To exercise any of these rights, contact us at vtprivacy@visualizetechnologies.com. We will not discriminate against you for exercising your privacy rights.

Notice at Collection for California Residents

This notice tells California residents what personal information we collect and why, at or before the time we collect it. (The CCPA applies only to businesses above certain sizes; we give this notice to everyone.)

  • Identifiers (name, email address, user ID, device ID, Apple sign-in details): to run your account, sync your data, provide support and keep the Service secure. Kept until you delete your account.
  • Biometric information, which is sensitive personal information (body scans, face photos, face data, the 3D model): to provide the Service and, only with consent, to test and train our own software. Kept on the schedule in our Biometric Data Retention and Destruction Policy.
  • Health information, which is sensitive personal information (measurements, body-composition estimates, Health & Safety answers including pregnancy status, Apple Health data, food allergies and logs): to provide the Service. Apple Health data is used only for your own targets. Kept until you delete it or your account, and on the same schedule as scans.
  • Racial or ethnic origin, which is sensitive personal information (ethnicity, only if set in a profile): to adjust body-composition and calorie estimates. Kept until you change it or delete the profile or your account.
  • Characteristics such as age and sex: to calculate measurements, estimates and targets. Kept until you delete the profile or your account.
  • Inferences (body-composition estimates and predictions): to provide the Service. Kept with the scans they come from.
  • Commercial information (subscription purchases, gym plan payments): for billing and accounting. Kept as business records for as long as tax and accounting law requires.
  • Internet or other electronic activity (app usage, diagnostic logs, crash reports): to find and fix problems. See "Diagnostic Logs" for how long they are kept.

We don't sell or share personal information, including sensitive personal information, and haven't in the past 12 months. For the full details, including who receives personal information, see the rest of this policy.

Data Breach Notification

In the event of a data breach that compromises your personal information, we will notify affected users as required by applicable state and federal law. All 50 states, the District of Columbia, and U.S. territories have data breach notification laws that we comply with.

  • Notification will be provided within the shortest timeframe required by applicable law (as few as 30 days in Colorado and Florida)
  • We will notify applicable state Attorneys General as required by each state's law
  • For health data breaches, we will also notify the Federal Trade Commission (FTC) within 60 days as required by the FTC Health Breach Notification Rule
  • Notification will include details of what data was affected and guidance on protective steps you should take

We encrypt data at rest (AES-256) and in transit (TLS). Some state laws don't require a notice when stolen data was encrypted and the key wasn't taken; we don't rely on that to skip a notice we owe, and we notify whenever the law requires it.

Changes to This Policy

We may update this Privacy Policy from time to time. We post the new Privacy Policy on this page with a new "Last updated" date, and we notify you of significant changes through the app or by email. We won't use personal information we already have in a materially different way from what this policy said when we collected it unless you agree, and we ask for consent again before we use biometric or consumer health data for a new purpose.

Contact Us

If you have questions about this Privacy Policy, please contact us: