WEBdiCOM
🔒 Privacy by design

Your DICOM stays in your browser

WEBdiCOM never uploads your scans. When you open a DICOM folder, a .zip, or load a direct URL, the files are read and rendered entirely on your own device. They are not sent to our servers — because there is no server doing the processing.

Our server only delivers the app itself (the HTML/JavaScript). Once your browser has loaded it, all the work — unzipping, reading the DICOM, building the 3D volume, rendering, and exporting — happens locally. We never see your images.

Why this is better for you

The one thing to know about “Load URL”

If you paste a direct file URL, your browser downloads that file straight from that host to your device — still not through our servers. Share-page links (WeTransfer, Google Drive, Dropbox, etc.) are intentionally not supported, precisely because making them work would require routing your file through a server. We'd rather keep your data local and ask you to download the file and drag it in.

What we do collect (anonymous)

To understand how much WEBdiCOM is used, we count basic anonymous events: a page visit, that a scan was loaded, and that an export happened (and its format) — plus a country (from your network, via our CDN) and a random id stored in your browser to estimate unique visitors. That's it. No images, no file names, no patient information, and no personal identifiers are ever collected or transmitted — only these aggregate counts.

In short

The trade-off is simple: your device does the heavy lifting, and in return your medical data stays private and never touches our infrastructure.

WEBdiCOM is for visualization, research, and education — it is not a certified medical device and not intended for clinical diagnosis.

← Back to WEBdiCOM