Everything you need to assess us as a supplier, in one place. Last updated [date]. Anything we have not answered here: [info@domain]
LayonMed 3D imports volumetric image data, segments it, reconstructs and edits 3D geometry, measures it and exports it. It is delivered as a hosted service.
You are responsible for validating the tool within your own quality management system and for the conformity of what you make with it.
We make that straightforward. Our Validation & Compliance Pack contains:
Request the Validation & Compliance Pack
Most tool vendors leave you to invent your own validation. We ship you one.
Controls marked planned are not yet in place. We would rather tell you that than have you find out.
| Hosting | [provider] — [Switzerland / EEA region] only |
|---|---|
| Data location | [Switzerland / EEA]. No processing or storage outside this area. |
| Authentication | Individual named accounts, each bound to a unique email address. No shared credentials. |
| Password storage | scrypt key derivation (n=16384, r=8, p=1) with a unique 16-byte random salt per account. Passwords are never stored or logged in recoverable form. |
| Password policy | [state the minimum length in force — see our note before publishing] |
| Session tokens | Generated with a cryptographic random source, stored only as a SHA-256 digest, time-limited, and compared in constant time. Sign-out revokes immediately. |
| Multi-factor authentication | Planned — target [date] |
| Failed-login limiting | Planned — target [date] |
| Session isolation | Each session runs in its own isolated host environment; case data is removed on teardown. |
| Encryption in transit | TLS for all traffic; session media encrypted in transport. |
| Encryption at rest | Planned — target [date] |
| Access logging & audit trail | Planned — target [date] |
| Rate limiting & request caps | Applied to session creation, requests and upload size. |
| Backup & tested restore | [state the schedule and the date of the last tested restore, or "planned — target [date]"] |
| Vulnerability management | Third-party components are inventoried and monitored against published advisories; corrective releases are issued and affected customers notified. |
| Penetration testing | [last date, or "planned — target [date]"] |
| Security contact | [security@domain] — coordinated vulnerability disclosure policy |
No third-party loading. LayonMed 3D loads no third-party code or content at runtime — no content delivery network, no third-party fonts, no analytics, no embedded widgets. Setting up the video connection does contact a public STUN server, and where a direct connection is not possible the encrypted video is carried by a TURN relay; both see your IP address and neither receives image or account data (see the privacy notice). The delivered application contains exactly two third-party components, both under permissive licences and both fully attributed: third-party software notices.
| Roles | For data you upload, you are the controller and we are the processor. A Data Processing Agreement must be in force before any upload. |
|---|---|
| Data Processing Agreement | Available here, pre-signed by us |
| Sub-processors | Listed here, with advance notice of any change you can subscribe to |
| Lawful basis | You are responsible for the lawful basis of the data you upload and for informing data subjects. |
| Impact assessment | The DPIA is the controller's obligation, so it is yours. We assist by providing the processing and security information you need. |
| Breach notification | We notify you without undue delay, with the information you need for your own notification. You notify the authority. |
| Retention & deletion | Per the Data Processing Agreement. Guest session data is deleted at session end or within [24 hours]. |
| Data minimisation | We ask you to upload pseudonymised data only — a case reference rather than a name. |
| Identifiability | We make no anonymisation claim. Cross-sectional imaging of the head and face remains identifiable after header identifiers are removed. Such data is pseudonymised, never anonymous. |
| Privacy Notice | Read it here |
| Version identification | The running version and build are displayed in the application. You can always see what you are using. |
|---|---|
| Release notes | Published with every release, stating whether the change can affect computational output and what we recommend you re-verify. |
| Known anomalies | Published with every release, stating plainly whether each can affect an output. |
| Change notification | At least [30] days' notice before any change capable of affecting computational output. |
| Version pinning | Available. Your environment stays on the version you accepted, so a service update cannot invalidate your validation. Ask for it in your Order Form. |
| Corrections | A defect capable of producing an incorrect output is corrected without delay, with immediate notification identifying the affected versions and dates. |
| Declared accuracy | No accuracy figures are currently declared. You must establish the accuracy achieved in your own workflow. Reference datasets with declared true dimensions are provided to help you. |
| Availability | [target, or "no availability commitment is given"] |
| Status | Service status |
| Support | [channel, hours, response targets] |
| Data export | Open formats, at any time. |
[Full legal name], [legal form] · [address], Switzerland
Commercial register [number] · VAT [number]
General [info@domain] · Data protection [privacy@domain] · Security [security@domain]