Privacy & data
Measurements are computed on the member's phone and stay there by default. Nothing about a member's body reaches Visualize unless you deliberately turn it on.
What lives where
| Data | Where it lives |
|---|---|
| Measurements & the 3D point cloud | On the member's device, in the app's private storage. Also in your app's memory as the ScanResult. |
| Scan happened (billing) | Visualize — scan_id, host_user_ref, model version, outcome. No measurements. This is the scan.completed event. |
| Measurements, server-side | Only if you enable results delivery: stored by Visualize and delivered to your backend. |
The default
With results delivery off (the default), the platform learns only that a scan happened, for which host_user_ref, and how it ended — never a body measurement. The member's results are theirs and yours, on the device.
If you turn on delivery
Enabling results delivery stores each result and sends it to your backend. Enabling it is your warranty that your app has each member's consent to that storage and delivery. You can delete a member's stored results at any time:
| Obligation | How |
|---|---|
| Member consent | Your app collects it; enabling the switch is your warranty you did |
| Deletion on request | Call DELETE /v1/results — see Results delivery |
Residency
Platform data (billing events, and stored results if you enable delivery) is hosted in the United States.
Turning delivery off stops new storage and delivery; it does not bulk-erase what was already stored. Use the deletion endpoint per member, which is the shape privacy requests actually arrive in.