App analysis · 12.10.2026
Dr. Max
eu.drmax.mobile · version 6.3.0
In short
SDKs found: 16. Companies: 11, of which outside the EEA — 9. Sensitive permissions: 9 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Firebase Cloud Messaging — Google LLC, United States outside EEA push notifications
- Firebase Crashlytics — Google LLC, United States outside EEA crash reporting
- Firebase Performance Monitoring — Google LLC, United States outside EEA performance monitoring
- Firebase Remote Config / A/B Testing — Google LLC, United States outside EEA удалённая настройка / A/B-тесты
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- ironSource — Unity Technologies, Israel outside EEA advertising
- Unity Ads — Unity Technologies, United States outside EEA advertising
- Adjust — Adjust GmbH, Germany EEA атрибуция установок
- AppLovin — AppLovin Corp., United States outside EEA advertising
- AppsFlyer — AppsFlyer Ltd, Israel outside EEA атрибуция установок
- Chartboost — Chartboost, United States outside EEA advertising
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- Microsoft Clarity — Microsoft, United States outside EEA запись сеансов
- Singular — Singular Labs, United States outside EEA атрибуция установок
- Stripe — Stripe, Inc., United States outside EEA payments
- Usercentrics — Usercentrics GmbH, Germany EEA consent platform
Sensitive permissions (9)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - camera —
android.permission.CAMERA - NFC: reading cards, documents and tags —
android.permission.NFC - steps —
android.permission.health.READ_STEPS - advertising ID (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_AD_ID - ad attribution (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_ATTRIBUTION - ad interests (Privacy Sandbox Topics) —
android.permission.ACCESS_ADSERVICES_TOPICS - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (22)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_ADSERVICES_CUSTOM_AUDIENCEandroid.permission.ACCESS_ADSERVICES_TOPICSandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.WAKE_LOCKandroid.permission.health.READ_HEALTH_DATA_HISTORYandroid.permission.health.READ_HEALTH_DATA_IN_BACKGROUNDandroid.permission.health.READ_STEPScom.android.vending.CHECK_LICENSEcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_IDeu.drmax.mobile.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
Limits of the analysis
The analysis shows code inside the app file, not data transfers: an SDK being present means a transfer is possible, not that it happens. The country is where the company owning the SDK is registered, not where its servers are. Some code may have been renamed at build time, so the SDK list is a lower bound.
The legal assessment is made by the competent supervisory authority.
Evidence
eu.drmax.mobile · version 6.3.0 (code 201)d06f2fb39c7e60aa86278911f0ebf739bf5a8bdaf92df1dff306d5bd40017c9cfe0d9a4a6a811f7d5572456c3a09c6f2abf4c2cde7d2cf2af0e71f509d64cebc13c27d15ac2eThe same file (same SHA-256) with the same library version gives the same result — check it on the APK check page. Licence CC BY 4.0, source — gdpru.eu; report errors to contact@gdpru.eu.