App analysis · 11.10.2026
ApoApp Apothekerkammer
at.apothekerkammer.apoapp · version V2.0.2
In short
SDKs found: 1. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 3 — 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
Sensitive permissions (3)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - camera —
android.permission.CAMERA
All manifest permissions (15)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CAMERAandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONSandroid.permission.SCHEDULE_EXACT_ALARMandroid.permission.VIBRATEandroid.permission.WAKE_LOCKat.apothekerkammer.apoapp.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.android.vending.CHECK_LICENSEcom.google.android.c2dm.permission.RECEIVE
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
at.apothekerkammer.apoapp · version V2.0.2 (code 95)3fa22f71066b3923ca5c3b35b7e85524632ce713d6ffee117f2c3078f81af6942f122b042bc47e29b2afe4294cfa0295cdde386f839ade947a20bc03ba8cf1f82769b78c1753The 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.