Spotlight & Quick Look PHI boundary
The packaged macOS app never indexes DICOM tag values into the system-wide Spotlight index or a Quick Look cache.
Desktop app only
Problem
The desktop build packages the application as a native macOS .app. macOS lets any bundle register a CoreSpotlight importer, a Uniform Type Identifier metadata importer (mdimporter), or a Quick Look content extension (qlgenerator) that reads a file’s content and writes derived metadata into a system-wide index or thumbnail cache. If dcmage ever registered one of these for .dcm files, Patient Name, MRN, and Date of Birth would end up in the macOS Spotlight index and a Quick Look thumbnail cache, outside the application’s own process boundary, surfaced by unrelated tools (Spotlight search, iCloud/Time Machine backups, third-party indexers), and surviving even after the app itself is deleted.
Boundary
dcmage does not register any of these system-level content extensions. The packaged bundle and build configuration are the enforcement surface:
- No CoreSpotlight importer,
mdimporter, orqlgeneratortarget is declared insrc-tauri/Cargo.toml,tauri.conf.json, the hardened-runtime or App Store entitlements, orpackage.json. - Fast in-app search (⌘/Ctrl+K) stays isolated to the application’s own local history. It never touches Spotlight.
- A native Quick Look thumbnail generator for
.dcmfiles is out of scope for this release; it is deferred and, if built, must render pixel data without burning in demographic overlays unless anonymize mode is active.
DICOM files accepted through the in-app feedback channel are a separate, already-implemented control: they are routed through the attachments/dicom/ storage prefix and swept after 7 days (rather than the standard 90-day retention), independent of this boundary.
Result
A check scans the packaged bundle and build configuration for Spotlight, mdimporter and qlgenerator markers and fails if any is present, including a plugin or target added later.