Privacy policy
Effective 27 July 2026 · approved policy version 1.0
CardioVisum is designed to keep clinical data private and under the user’s control.
Data we process
We process account details, selected DICOM series, retained clinical metadata, generated NIfTI images, segmentations, measurements, edits, and reports.
Storage and sharing
Data is stored on a private server and served only through authenticated endpoints. Authorized CardioVisum administrators may access cases for operations, security, support, and approved research governance.
De-identification
Optional local de-identification removes direct identifiers and private tags before selected data is uploaded. Burned-in text requires human confirmation.
Retention and deletion
Cases are retained until you or an administrator deletes them. Deletion cancels work and schedules protected file cleanup; backups expire under the deployment’s approved retention schedule.
Model improvement
By using this service, you agree that reviewed segmentation edits may be used to improve future models.
Important limitations
CardioVisum cannot guarantee detection of burned-in pixel identifiers, does not provide a formal clinical access-audit trail, and cannot guarantee that all imaging data is non-identifiable.