LayonMed3D

Privacy notice

Draft - last updated 2026-08-07. Contact: [CONTACT EMAIL]

Who is responsible

[OPERATOR NAME], [STREET, POSTCODE, CITY, SWITZERLAND], is the controller for the personal data processed by LayonMed 3D.

What we process, and why

• Medical images you upload (DICOM/NIfTI/NRRD) and everything you derive from them (masks, 3D objects, measurements, saved projects). These are stored on our workstation in Switzerland so the software can process them and so you can reopen your work. Legal basis: your consent, which we ask for before you start.
• Account data: your email address and a hashed password (we never store the password itself). Basis: performance of the contract to provide you the service.
• Usage and diagnostic records: sign-in times, session duration, which tools you use, errors, and performance measurements. We use these to keep the service working and to find faults. Basis: our legitimate interest in a reliable, secure service.

Patient data - your responsibility

If the images you upload contain patient data, you are the controller for that data and you must have a lawful basis to process it and to share it with us as your processor. Please pseudonymise images where you can. Do not upload data you are not permitted to share.

How long we keep it

Account data and saved projects: until you delete them or ask us to close your account. Uploaded images: kept so you can continue working with them; tell us if you want them removed. Guest sessions are not stored as projects, but uploaded images and usage records may still be retained as described above. Diagnostic records are kept for a limited period for troubleshooting.

Who else sees it

Your browser contacts a public STUN server operated by Google (stun.l.google.com) while setting up the video connection. That server sees your IP address; it carries no image data and no account data. Where a direct connection is not possible, the video is relayed through a TURN relay, which also sees your IP address but cannot read the encrypted media.

The service runs on our own hardware. Network traffic passes through Cloudflare (as a transport provider) to reach us. We do not sell data and we do not use it for advertising.

Your rights

You can ask for access, correction, deletion, restriction, a copy of your data, or to withdraw consent (which does not affect processing already carried out). Write to [CONTACT EMAIL]. Under the Swiss revFADP you may also contact the FDPIC; under the GDPR, your local supervisory authority.

Cookies and local storage

We use only what the service needs to work - there is no advertising, no tracking and no third-party analytics, so there is no cookie banner to click away.

• lo3seat (cookie, 30 days, HttpOnly) - binds your browser to the workstation session serving you, so returning to the link brings you back to your own session.
• Session storage (cleared when you close the tab): your sign-in token, the session id, and reconnect state.
• Local storage: your sign-in token for returning on the same device, and interface preferences such as panel order and display settings.

All of these are strictly necessary for a service you asked for, or store a preference you set. If we ever add analytics or anything from a third party, we will ask for your consent first.

Security

Traffic is encrypted in transit (HTTPS). Passwords are stored hashed. Access to the workstation is restricted to the operator.