DICOM-Swift privacy policy

Scope and local processing

This policy describes the DICOM-Swift package and bundled CLI. An application that embeds the package has its own storage, sharing, and service policies.

The parser reads the DICOM metadata and pixel data supplied by the caller. Those inputs may contain patient identifiers, clinical information, private tags, or identifying text burned into pixels. Local file decoding does not require an upload to the package developer.

Network features

When the host invokes networking features, DICOMweb and DIMSE requests can send query criteria, datasets, images, and authentication information to the configured server. JPIP retrieval uses a caller-provided transport.

Server operators determine their own logging and retention. The library does not make every network connection encrypted automatically; deployment code must configure the appropriate transport, endpoint permissions, and credentials.

Files and exports

Image exports, DICOM rewrites, received instances, and extracted archives may create files in locations selected by the caller or temporary storage. CLI inspection can print metadata to the terminal.

Image export defaults to no metadata sidecar, but images and annotations may still identify a person. De-identification helpers do not by themselves establish that every output is safe to share, including burned-in text. Review files before sending them elsewhere.

Diagnostics and credentials

The package supports local diagnostic logging and caller-supplied audit or codec reporting callbacks. These are integration hooks rather than a developer-hosted analytics account. Error messages can contain file paths, request URLs, or response previews.

Connection credentials are supplied by the host; the package does not provide an end-user credential vault. The host controls any storage or forwarding of logs and secrets.

Retention and removal

The caller controls input files, output files, archives, caches, and any application database. Remove those items through the host application or filesystem as appropriate. Stopping local use does not delete copies already sent to a DICOM server, exported elsewhere, or kept in backups.

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.