ThalesMMS

IsiX DICOM Viewer for macOS / Privacy

IsiX DICOM Viewer for macOS privacy policy

Effective October 3, 2026

How IsiX DICOM Viewer for macOS handles data, including the services and integrations you choose to use.

Read the data collection declaration

Scope and developer

This policy applies to the Mac App Store edition of IsiX DICOM Viewer for macOS, the Horos-derived application maintained by Thales Matheus M Santos. Other applications and distribution editions have separate privacy terms.

The application is an image viewing tool. It is not for diagnostic use.

Data received by the developer

The app does not send your DICOM files, patient information, credentials or viewing activity to the developer. It does not use a developer-hosted study server, advertising, tracking or an external analytics backend. No developer account is required to view local files.

The app does not configure an automatic crash-report upload destination. Support messages you choose to send are described separately below.

Local files and study data

The app processes DICOM images, patient metadata, study indexes, measurements, annotations and derived viewing data on your Mac. These files can contain sensitive information in both their metadata and image pixels.

The default database is stored in application storage protected by App Sandbox. Files and external database folders selected through the macOS file picker can be read or written for the requested operation. Folder access may be remembered for later use.

Finder previews and thumbnails process selected DICOM files locally. Your operating system, backup software or a storage service you choose may maintain additional copies.

Network connections and sharing

DICOM and DICOMweb queries, retrievals and sends communicate directly with the archive endpoints you configure. Those systems receive the search criteria, identifiers, authentication information or DICOM objects needed for each operation. Imports from a URL contact the address you provide.

Automatic query, retrieve or routing rules can initiate transfers after you enable them. Receiving and sharing services can make study data available to devices allowed by your configuration. These endpoints are selected by you and are not developer-operated collection services.

Exports, email or sharing actions create copies for the destinations and recipients you choose. The receiving system or person controls those copies. Check patient identifiers and burned-in image text before sharing.

You can cancel transfers, disable automatic rules and receiving or sharing services, or quit the app to stop its active services. Remove connections and credentials you no longer want to use.

Credentials and security

DICOMweb authentication credentials are stored in the macOS Keychain and used for the configured endpoint. Connection preferences and study data remain in the storage you use for the app.

TLS and HTTPS are available for compatible servers. Protection depends on the connection and server settings. App Sandbox and Keychain storage do not mean that every study file or network transfer is encrypted.

Diagnostics

Diagnostic logs and crash information can be generated locally. They can include file paths, system details or information about the operation that failed. The app does not automatically upload these records to the developer.

If you choose to send a log or diagnostic file with a support request, review its contents first. macOS and the App Store may handle diagnostics under Apple's own settings and privacy practices.

Retention and deletion

Local studies and associated data remain in their configured storage until you delete them or a configured cleanup rule removes them. Use the database controls to manage local studies and review the selected deletion options.

Deleting a local study does not recall a transfer, delete an archive's copy, or remove separately exported files and backups. Manage those copies with the receiving system or storage provider. Removing the app also does not guarantee removal of external folders, exports or Keychain credentials.

Optional support correspondence

If you contact the developer by email, the developer receives your email address and the information or attachments you choose to provide. These are used to respond to the request and investigate the reported problem, not for advertising, profiling or sale.

Support correspondence is retained while needed to handle the request and related follow-up. You can request access, correction or deletion by emailing the address below. Do not include patient data, passwords, tokens or private documents.

This support website

This static website does not use analytics scripts, forms, or third-party tracking scripts. GitHub Pages handles requests to the website under its own hosting and privacy practices. Visiting a source repository or contacting another service is subject to that service's policies.

Privacy questions and support

Contact Thales Matheus M Santos about IsiX DICOM Viewer for macOS at thalesmmsradio@gmail.com.

If you email us, we receive your email address and the information you choose to send to respond to your request. Please omit patient information, private documents, and credentials.

Policy updates

This policy may change when the software's data handling changes. The effective date above identifies this version. Features and integrations can differ by release and platform.