Privacy & security
What PreviewMD does with patient data
A patient uploads one photo on your website and enters their name and email to see an accurate picture of how they could look after a procedure. That’s three pieces of information, and each one is handled differently.
Everything a patient gives you
The photo, the contact details, and the record that it happened.
The photo
Discarded after the render
The photo goes to the model that generates the picture. After that render it’s discarded. PreviewMD keeps no patient images, on any plan, for any length of time. There’s no archive to search, no gallery to administer and no retention window to configure, because nothing is being retained. Nothing in the product writes a patient image to disk.
Name and email
Passed to your system, never stored here
The patient enters their contact details to unlock the picture, and those details go straight to your own system through whichever delivery route you set up. The lead transits PreviewMD on its way to you. The payload isn’t logged, isn’t written to disk and isn’t held in storage for retry if delivery fails. If a delivery does fail, the record carries that status so you can see it in your dashboard.
The usage record
Kept, and identifies nobody
Every preview writes one row to our database. It holds which procedure was previewed, the page on your site it ran on, whether delivery to your system succeeded, and the time it happened. No name, no email address, no phone number, no photo. Your dashboard shows that a capture happened and which page it came from; the contact information itself lives in your CRM.
HIPAA and BAAs
PreviewMD doesn’t claim to be HIPAA compliant.
Here’s the mechanism instead, so you can judge it yourself. The widget never asks for medical history. It never receives a chart, a diagnosis or an insurance record, and it doesn’t connect to your EHR. The only patient information it touches is a photo it discards and contact details it hands to you.
A BAA governs protected health information a company holds on your behalf. PreviewMD holds none, so there’s nothing for a BAA to cover.
Consent
What the patient sees before they upload.
Two things, in plain language, on the widget itself. That their photo is processed once to create the visualization and is never stored. And a consent line they tick before anything is sent:
“I consent to being contacted about scheduling a consultation. My information will be shared with this practice only.”
Application security
How the application is secured.
- • Every connection is encrypted, and browsers are told to refuse an unencrypted one.
- • The widget can use a camera, because it takes photos. It cannot use a microphone or read location.
- • No other site can load your widget inside a frame and pass it off as theirs.
- • Your embed code is locked to your domain, so another practice can’t lift it onto theirs.
- • Passwords are stored as one-way hashes, so nobody can read them back, including us.
- • The application itself is kept out of search results entirely.
Scope
What PreviewMD is not.
A preview is a visualization that supports your consultation. It isn’t a clinical projection, a diagnosis or a guarantee of outcome, and individual results vary. PreviewMD isn’t a medical device. It doesn’t write to a chart, schedule anything or touch billing.
Questions
What practices ask about patient data.
Do you store patient photos?
No. A photo is used once to generate the picture and is then discarded. PreviewMD keeps no patient images, on any plan.
Is PreviewMD HIPAA compliant?
PreviewMD doesn’t claim to be. The widget never asks for medical history, never receives a chart or a diagnosis, and doesn’t connect to your EHR. The only patient information it touches is a photo it discards and contact details it passes to your system.
Do I need a BAA with PreviewMD?
A BAA governs protected health information a company holds on your behalf. PreviewMD holds none, so there’s nothing for a BAA to cover.
Where do the patient’s contact details end up?
In your own system, through whichever delivery route you set up. PreviewMD passes them through without storing them.
What does PreviewMD keep in its own database?
One row per preview: the procedure, the page it ran on, whether delivery succeeded, and the time. No name, no email address, no phone number and no photo.
Can another practice copy my embed code?
No. Your embed code is locked to your domain, so it won’t run on another site.
See your result before you decide.
14 days free on any plan. Card up front, cancel anytime.