DICOM tools for AI agents / Privacy
DICOM tools for AI agents privacy policy
Effective September 5, 2026
How DICOM tools for AI agents handles data, including the services and integrations you choose to use.
PACS and network operations
Query, retrieve and send commands communicate with configured DICOM systems. Integrated DICOMweb support uses configured HTTP endpoints and credentials. Installation may download Python or Node dependencies; optional Orthanc use may download a container image.
Agent and chat host access
Local execution does not make an agent workflow private from its host. Tool output, prompts, file paths and rendered images may be handled by the configured agent or chat service.
Rendering paths differ
The integrated interactive workflow routes sensitive widget data through MCP result metadata and uses opaque selection tokens. This does not remove the chat host from the rendering path. The separate prototype embeds rendered PNG images and image information in an HTML resource delivered to its MCP host.
Files and retention
Retrieved DICOM, prepared copies, manifests, HTML viewers, PNGs, videos and encapsulated PDFs are local artifacts that can remain after a session. Stopping a temporary Orthanc container does not by itself purge its data directory; review explicit purge options and delete outputs according to your own policy.
Anonymization limits
Metadata anonymization does not remove burned-in pixel annotations. PDF encapsulation preserves the supplied document bytes, and previews can expose visible patient information. Review outputs even when a summary mode reduces identifiers in command output.
Configuration and exposure
Protect configuration files and credentials. Use the separate viewer’s stdio transport for local host integration: its HTTP mode binds all interfaces and enables CORS, without an application authentication flow in the inspected entry point. The integrated viewer uses a loopback HTTP bind.
Providers and telemetry
No dedicated first-party analytics service was identified in the inspected tools. AI provider processing, chat history, connector logging and retention depend on the agent host and configured services; they are outside these libraries’ controls.
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 DICOM tools for AI agents 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.