Privacy and safety
The honest before-and-after.
We built GlimpseMD so a clinic can help patients picture a result without overpromising one, and without building a database of patient faces.
Where the photo goes
01
On the patient's device
Quality checks, face-feature positioning, and the final likeness check all run in the browser. Feature measurements never leave the device.
02
One generation, in memory
The photo is sent to our servers and to the AI image service once, held in memory for that request, and discarded. GlimpseMD writes no photo or result to disk or a database.
03
The AI provider
The image provider may keep API inputs for up to 30 days for safety monitoring, then deletes them. We say so in the consent step. We are applying for zero-retention processing and will update this page when it is in place.
04
What we keep
Clinic settings and usage counts: which service was explored, when, and whether a result was shown. Never the photo, the result, or the patient's contact details.
Safety rules that are built in, not bolted on
Likeness checks
Always labeled
Adults, self-images, consent
What GlimpseMD is not
- Not a medical device, diagnosis, treatment plan, or outcome prediction.
- Not for patient records, medical imaging, or protected health information.
- Not a source of before-and-after photos for advertising. Clinic terms forbid using simulations that way.
- Not face recognition. Feature measurements are used once to position an edit and are never matched, stored, or reused.
Privacy policy · Consumer health data policy · Terms of service
Questions about compliance?
We are happy to walk your practice manager or compliance lead through the full pipeline.