App analysis · 17.10.2026
FLauncher
me.efesser.flauncher · version 0.18.0
In short
SDKs found: 3. 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 Crashlytics — Google LLC, United States outside EEA crash reporting
- Firebase Remote Config / A/B Testing — Google LLC, United States outside EEA удалённая настройка / A/B-тесты
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
Sensitive permissions (2)
- advertising ID —
com.google.android.gms.permission.AD_ID - request to delete apps —
android.permission.REQUEST_DELETE_PACKAGES
All manifest permissions (6)
android.permission.ACCESS_NETWORK_STATEandroid.permission.INTERNETandroid.permission.REQUEST_DELETE_PACKAGESandroid.permission.WAKE_LOCKcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_ID
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
me.efesser.flauncher · version 0.18.0 (code 366)36e13a97d92dbfa038f5af3976b05d86ea504ed664dd2ed0a21f3b560ce19cb40dfffb6265da7a3397ee3f26003a0ae3bc10c6cbf568c811e1f1f8578d1d3bdc13c27d15ac2eThe 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.