App analysis · 11.10.2026
Apotea
se.apotea.app · version 1.0.8
In short
SDKs found: 4. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 2 — 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
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
Sensitive permissions (2)
- advertising ID (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_AD_ID - ad attribution (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_ATTRIBUTION
All manifest permissions (11)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.VIBRATEandroid.permission.WAKE_LOCKcom.android.vending.CHECK_LICENSEcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEse.apotea.app.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
se.apotea.app · version 1.0.8 (code 77)c1bf31d8714619a2b114ea07b67c13137677b065caef0e2dc01c3c57afc03f1bab07bbe6c802a38511ec5ec645a1c16ca6df1d80615d2a7cb2d0eadaa050dbe62769b78c1753The 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.