Privacy Policy

1. Who we are

This policy covers the Ossidex DICOM Viewer app for iPhone and iPad and the website ossidex.com. Contact: support@ossidex.com.

2. Your scans and medical images

• Processed on your device. DICOM, NIfTI and other files you import are decoded, stored and displayed inside the app on your device. They are not uploaded to our servers.
• Import from links. When you paste a link (for example Google Drive, Dropbox, OneDrive, iCloud Drive, WeTransfer, Yandex Disk or Mail.ru Cloud), the app downloads the file directly from that provider to your device. We do not receive or store the file. The provider’s own privacy policy applies to the link.
• PACS / DICOMweb. If you connect a PACS server, the app talks directly to the server you enter. Server passwords and tokens are stored in the iOS Keychain on your device.
• Your device backups. Studies stored in the app may be included in your own iCloud or computer backups of the device, depending on your settings.
• Deletion. Delete individual studies in the app, use Settings → Clear All Scans, or delete the app.

3. Information we collect

We do not collect medical images, DICOM files or their metadata, patient names or file names, your name, contacts or precise location.

Pseudonymous identifier. The app creates a random “Support ID” on your device (shown in Settings). It links analytics, crash reports and subscription status. It is not tied to your name or Apple ID.

Usage analytics (PostHog). Which features and screens are used, import and viewer outcomes and error types (for example “archive password required” or “link returned a web page”), app and iOS version, device model and memory class, language and App Store country. For link imports we record the service and host name (for example “drive.google.com”) and the shape of the link with identifiers removed — not the full link, file names or contents. Session recording is off. PostHog may derive an approximate location (country/city) from the IP address of the request.

App analytics and advertising measurement (Firebase Analytics / Google Analytics). We record first opens, app sessions, onboarding and paywall actions, device and app information, and a Firebase app-instance identifier linked to your random Support ID. Adapty can send subscription, trial, renewal and refund events to the same Analytics property, including product, currency and transaction value. We link Analytics with Google Ads to measure installs and paid campaign performance. IDFA collection and personalized advertising are disabled. Medical images, patient identifiers and file names are not sent to this service. Attribution may be aggregated or modelled rather than a complete record of individual users.

Crash and diagnostic reports (Firebase Crashlytics). Technical data about crashes and errors: device and OS, app state (for example viewer mode, number of slices, volume size, modality) and error codes.

Advertising attribution. If you installed the app from an Apple Search Ads ad, Apple’s AdServices framework tells us the campaign, ad group, keyword and country. The app does not use the advertising identifier (IDFA) and does not track you across other companies’ apps or websites.

Subscriptions (Apple and Adapty). Payments are processed by Apple. We use Adapty to manage subscription status, offers and paywalls; Adapty receives your Support ID, purchase and subscription events and device information. We never see your payment details.

Notifications. If you allow notifications, the app subscribes to Firebase Cloud Messaging topics (for example your language and subscription state) to receive messages about offers, trials and billing. We do not store your device token on our servers. You can turn notifications off in iOS Settings at any time.

Support messages. When you contact us from the app, we receive your message, the contact details you enter, your specialty if you choose one, app and iOS version, device model, language, your Support ID and a device identifier for this app, plus any attachments you add. “Report to support” from the viewer may add a diagnostic file (including the file name) and a DICOM header summary with patient identifiers removed. The website contact form sends your name, email and message (and, when opened from the app, your Support ID). Support messages are delivered to our team by email and a messaging service and kept only as long as needed to help you.

Website. ossidex.com uses Cloudflare Web Analytics, which counts visits without cookies. We do not use advertising trackers on the website.

Website traffic measurement. We count visits (30-minute inactivity sessions) and App Store button clicks by traffic source and page language. These aggregate counters contain no user identifier, IP address, full referrer, URL query, or medical data. Session storage on your browser keeps the source during navigation. App Store campaign tokens identify a source and language, not a person.

The same counter runs on the browser viewer page. Each request carries only the event type (visit or App Store click), the traffic source and the page language, without cookies or referrer. Files you open in the viewer are never part of it.

Browser viewer usage (Google Analytics 4). The browser viewer sends technical events for imports, the first displayed image, MPR, tools and App Store actions to an endpoint on ossidex.com. Events contain result categories, durations, ranges for file counts and sizes, browser and operating-system families, and page language. They do not contain file names, patient information, DICOM identifiers (UIDs), image or scan content, full URLs or raw error messages. We do not forward your IP address to Google.

A random session identifier exists only in memory for the current open page. This measurement uses no persistent cookies, stored user identifier or account identity. Our first-party database keeps aggregate counters without session identifiers. Our server forwards these technical events and the temporary identifier to a separate Google Analytics 4 web stream through Measurement Protocol, to connect the steps of an import attempt. It is not used to build a profile across devices or link browser activity to the native app. Session replay, advertising and personalization are disabled for this web stream.

4. Why we use it

• To make the app work, fix bugs and crashes and improve import and viewing (legitimate interests).
• To provide subscriptions, restore purchases and send billing-related messages (contract).
• To answer your support requests (contract / legitimate interests).
• To measure which ads bring users, without cross-app tracking (legitimate interests).

5. Service providers

• PostHog (USA) — product analytics
• Google Firebase (USA) — Firebase Analytics / Google Analytics, Crashlytics, Cloud Messaging, Remote Config, Cloud Functions for support messages
• Adapty — subscription management
• Apple — App Store payments, AdServices attribution, push delivery
• Google Analytics 4 (USA) — browser-viewer technical usage events sent by our server to a separate web stream
• Cloudflare — website hosting and cookie-free web analytics

These providers process data on our behalf under their own terms and may store it outside your country, including in the United States.

6. Retention

Scans stay on your device until you delete them. Analytics and crash data are kept for up to 14 months, then deleted or aggregated. Subscription records are kept as required for accounting and App Store purposes.

7. Your choices and rights

You can delete your scans at any time, turn off notifications in iOS Settings, and ask us to access or delete analytics and support data linked to your Support ID — send the ID (Settings → copy Support ID) to support@ossidex.com. Depending on where you live (for example under the GDPR or CCPA) you may also have the right to object, to restrict processing and to complain to a data-protection authority.

8. Patient data and your responsibilities

If you open patients’ images, you remain responsible for handling them under the rules that apply to you (for example HIPAA or your institution’s policies), including device security and how you share exports. Use anonymized export when sending studies to others.

9. Children

Ossidex is not directed to children and we do not knowingly collect data from children.

10. Changes

We will update this page when our data practices change and adjust the date above. Significant changes will be announced in the app.

11. Contact

Questions or requests: support@ossidex.com

Terms of Use