App analysis · 19.10.2026
Football League 2026
com.football.soccer.league · version 0.2.18
In short
SDKs found: 23. Companies: 14, of which outside the EEA — 13. Sensitive permissions: 7 — 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 AdMob — Google LLC, United States outside EEA advertising
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google User Messaging Platform — Google LLC, United States outside EEA consent platform
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- Meta Audience Network — Meta Platforms, United States outside EEA advertising
- ironSource — Unity Technologies, Israel outside EEA advertising
- Tapjoy — Unity Technologies, United States outside EEA advertising
- Unity Ads — Unity Technologies, United States outside EEA advertising
- Yandex Mobile Ads — Yandex, Russia outside EEA advertising
- Yandex Mobile Ads (monetization) ✓ — Yandex, Russia outside EEA advertising
- Adjust — Adjust GmbH, Germany EEA атрибуция установок
- AppLovin — AppLovin Corp., United States outside EEA advertising
- Pangle — ByteDance, China outside EEA advertising
- Chartboost — Chartboost, United States outside EEA advertising
- Fyber (Digital Turbine) ✓ — Digital Turbine, United States outside EEA advertising
- IAB Open Measurement SDK — IAB Tech Lab, United States outside EEA ad measurement
- InMobi — InMobi, India outside EEA advertising
- Vungle (Liftoff) — Liftoff Mobile, United States outside EEA advertising
- Mintegral — Mobvista, China outside EEA advertising
- myTarget — VK, Russia outside EEA advertising
Sensitive permissions (7)
- foreground service: screen capture —
android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - 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 (20)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_ADSERVICES_TOPICSandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_DATA_SYNCandroid.permission.FOREGROUND_SERVICE_MEDIA_PROJECTIONandroid.permission.INTERNETandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEandroid.permission.WRITE_INTERNAL_STORAGEcom.amazon.privacypass.ATTESTcom.android.vending.BILLINGcom.android.vending.CHECK_LICENSEcom.football.soccer.league.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.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
com.football.soccer.league · version 0.2.18 (code 218)a80b134f38512059263309d9e53b3e2a25d82e46bf29ffad7a3444ab1ae903d6c347a317b505c569950687d464cec22c89eb53f59e2f3953e58be2ada8978175The 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.