Privacy policy
DentCT Pro collects no data. This page explains what that means in practice, because the app handles medical images.
1. In short
- The app collects no data of any category. No account, no sign-in, no analytics, no advertising identifier.
- The app opens no network connections. It works in airplane mode.
- Studies you open stay on your device only.
- The manufacturer never receives, sees or stores a study, a patient name or a measurement.
2. Who the controller is
For the purposes of Regulation (EU) 2016/679 (GDPR), you — the practice, clinic or institution you work for — are the controller of the personal data contained in the studies you open. MSCS di Stefan E., as the manufacturer, does not process that data: it does not receive it, transmit it or have access to it. There is therefore no controller–processor relationship and no Article 28 agreement is required to use the app.
3. What the app handles, and where it stays
| Category | Where it goes | Who sees it |
|---|---|---|
| CT/CBCT images and their DICOM metadata (patient name, ID, birth date, sex, study date) | The app's container, on your device | Only you |
| Measurements, annotations, canal tracings, implant plans | A separate session file on your device | Only you |
| Display preferences | App preferences, on device | Only you |
| Technical logs | The system log, on device | Only you. Identifiers are replaced with short irreversible tags before they are written. |
Health data is a special category under Article 9 GDPR. In this app it is processed entirely locally.
4. How it is protected
- iOS and iPadOS: complete file protection — studies cannot be read while the device is locked.
- macOS: the app sandbox container; at-rest encryption comes from FileVault.
- Imported studies and working copies are excluded from iCloud and iTunes backups.
- Original files are opened read-only. The imported study is never modified.
5. What the app does not do
- Sends nothing to any server, the manufacturer's or anyone else's.
- Contains no analytics, advertising or crash-reporting SDK.
- Does not track across apps or websites and does not access the IDFA.
- Does not use HealthKit and does not write to the Health app.
- Does not access the camera, microphone, contacts, calendar or location.
The privacy manifest bundled with the app declares zero collected data types and three required-reason APIs: file timestamps, disk space and user defaults.
6. Sharing and export
Nothing leaves the device unless you explicitly export. The app offers de-identified DICOM export — showing you exactly what will be replaced, removed and regenerated before anything is written — plus PDF reports with an option to omit patient details, and PNG captures.
Important limitation: de-identification does not detect text burned into the image pixels. If a patient name is printed into the image, it remains visible.
7. Deletion
Deleting a study removes its index entry, its session and its working copy. Deleting the app removes everything it stored. There is nothing to delete "at the manufacturer", because the manufacturer holds nothing.
8. Children
Not directed at children. The 4+ rating reflects the absence of objectionable content, not a child audience.
9. Data subject rights
Because the manufacturer holds no data, patient requests for access, rectification, erasure or portability are addressed to the practice or institution operating the app.
10. Contact
- Manufacturer
- MSCS di Stefan E.
- Registered address
- [to be completed before publishing]
- support@support-remote.org