dicom-go privacy policy

Library and tool scope

This policy covers dicom-go and its bundled tools. Applications and servers built with it decide which datasets to accept, where to store them, who can access them, and which services to contact.

The library processes the DICOM metadata, images, files, and query parameters supplied to it. Local parsing does not need to send a dataset to the package developer.

Network requests and receivers

Calling DIMSE, DICOMweb, or JPIP features can send identifiers, queries, images, and authentication data to the configured destination, or receive datasets from a remote system. JPIP retrieval uses explicit host and scheme rules with origin-bound credentials.

Transport encryption is a deployment choice, not a guarantee for every command. The remote server can retain requests and transferred data under its own policies.

Persistent output and caches

File writers, exports, and storage receivers create local files. CLI dumps and DICOM JSON can disclose patient names, identifiers, or other metadata. JPIP retrieval also uses an in-memory response cache.

The operator controls storage locations and retention. Remove saved outputs and logs separately from the original data, and consider any filesystem backups or synchronization.

Audit and diagnostic integrations

The networking packages expose audit and telemetry callbacks for a host to consume. The structured telemetry event format excludes dataset values and raw packet payloads; endpoint details are omitted by default but can be enabled by caller policy. Separate audit records may include AE titles and addresses.

These callbacks do not constitute a built-in developer analytics upload. A host can write or forward records using its own sinks, and explicitly enabled raw traffic capture needs separate handling because packets can contain clinical data.

Credentials and de-identification

Applications supply and manage credentials and token sources. The library is not an end-user secret vault.

De-identification is an explicit operation with supported profiles and options. It is not automatic for ordinary reads, sends, or exports. Review identifying metadata, private tags, and burned-in pixel content before sharing; a rewrite alone is not a guarantee of anonymity.

Your controls

Stop listeners and network tasks to stop future transfers. Remove retained input copies, received files, exports, and operator-managed logs when no longer needed. Removal on your machine does not remove copies at a remote server or in a recipient's files.

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.