MIDRC · Privacy
Privacy policy
Updated: 9 October 2026 · Developer: Vladimir Lebedev (VSchwan)
1. Data on your device
MIDRC reads DICOM files and archives you select, makes local copies and stores an image library in its app container. Files may include health information, patient names and identifiers, dates and other personal data. Notes, favorites and annotations are stored locally. The developer does not automatically receive these data.
2. Data collection by the developer
The app has no developer account registration, advertising SDK, analytics SDK, tracking or automatic upload of studies to a developer backend. MIDRC does not collect advertising identifiers. Remote servers are used only for downloads or DICOMweb requests initiated by you.
3. Networking and third-party services
If you enter an HTTPS link or DICOMweb/PACS address, the app contacts that server. The selected server can receive your IP address, request parameters, a Patient ID entered for searching and a supplied Bearer token. Its operator handles these under its own policies. The app does not persist Bearer tokens between import-screen sessions; the server address is stored in preferences. Use only servers you are authorized to access.
4. Import and export
External documents are selected through the system file picker. You initiate exports and sharing. The selected app, service or recipient receives the exported data and processes it under its own policies. Original DICOM, images, measurements and text burned into pixels can contain personal information. Clearing metadata does not guarantee anonymization and does not remove text in image pixels.
5. Protection and backups
MIDRC uses the iOS app container and system file protection. An optional Face ID/device-passcode lock can be enabled in Settings. Apple LocalAuthentication performs the identity check; the app and developer do not receive facial data or the device passcode. This is not separate end-to-end encryption of the library. Device backups may include app data, depending on your Apple settings and services.
6. Retention and deletion
Studies stay on the device until you delete them from the study-card menu or uninstall the app. Deleting a study removes its local DICOM files, note, favorite state and saved frame annotations. Copies previously exported to other apps, servers or backups must be deleted separately. Support messages are retained for responding to and resolving the inquiry; request deletion through the support email.
7. Support and children
If you email support, the developer receives your sender address and message content. Do not send identifiable patient data or original studies without necessity and appropriate authorization. MIDRC is not specifically intended for children and does not automatically collect their data.
8. Changes and contact
This policy may change when app functionality changes. The current version is available in the app and on this page. The developer is Vladimir Lebedev (VSchwan). For privacy inquiries or support-message deletion, contact [email protected].
9. This website
This public website is separate from the app. It does not accept uploads of studies and does not embed analytics, advertising pixels or third-party fonts. Web requests are processed by the hosting server and Cloudflare to deliver and protect the site. Technical data can include IP address, requested URL, timestamp, browser/user-agent and response status in server or security logs. Do not put patient information or secrets into URLs. Advertising identifiers already listed in app-ads.txt do not install advertising or tracking in MIDRC. A future advertising or analytics integration will require updated disclosures before activation.