MTK — Metal Toolkit privacy policy

Scope of the toolkit

MTK is a library embedded in a host application. This policy covers its rendering core, not every application that uses it. The host application owns DICOM parsing, access permissions, user accounts, and network integrations.

Data processed on the device

MTK receives decoded voxel buffers, dimensions, spatial information, transfer functions, and related rendering inputs from its caller. It creates CPU and GPU resources on the device to render those inputs.

The audited rendering core has no built-in service that uploads volumes to the developer. This does not describe the network behavior of a host application or its other dependencies.

Local logs and settings

The toolkit writes diagnostic messages to the console and local log files. Additional high-frequency performance logging can be enabled by the host. Log messages and labels supplied by an integration may reveal details about its data or workflow.

Metal availability results can be saved in application preferences when the caller supplies a preferences store. The toolkit does not provide a separate user account or credential store.

Snapshots and sharing

Explicit snapshot export writes rendered PNG files to a caller-selected destination. An image can contain sensitive anatomy or information added by the host. Rendering or exporting an image does not anonymize its content.

Retention and host responsibilities

The host controls the lifetime of volume buffers and caches, saved snapshots, application preferences, and local logs. It also controls backup or synchronization of those files. Use the host application and filesystem controls to remove persistent outputs; the rendering package does not offer an end-user deletion screen.

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.

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.