App analysis · 14.10.2026
Boots
com.boots.flagship.android · version 43.0
In short
SDKs found: 15. Companies: 6, of which outside the EEA — 6. Sensitive permissions: 8 — 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 Dynamic Links — Google LLC, United States outside EEA attribution / глубокие ссылки
- Firebase In-App Messaging — Google LLC, United States outside EEA маркетинг / push
- 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 Analytics — Google LLC, United States outside EEA analytics
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google Tag Manager — Google LLC, United States outside EEA диспетчер тегов
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- Adobe Experience Platform Mobile SDK — Adobe Inc., United States outside EEA analytics
- Airship — Airship, United States outside EEA маркетинг / push
- Amplitude — Amplitude Inc., United States outside EEA analytics
- WeChat OpenSDK — Tencent, China outside EEA social login
Sensitive permissions (8)
- 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 - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - fingerprint —
android.permission.USE_FINGERPRINT - advertising ID (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_AD_ID - ad attribution (Privacy Sandbox) —
android.permission.ACCESS_ADSERVICES_ATTRIBUTION
All manifest permissions (22)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CAMERAandroid.permission.FLASHLIGHTandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.SCHEDULE_EXACT_ALARMandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTandroid.permission.VIBRATEandroid.permission.WAKE_LOCKcom.android.launcher.permission.INSTALL_SHORTCUTcom.boots.flagship.android.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
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.boots.flagship.android · version 43.0 (code 62314770)649201681cc3a4441f69354ffc2a81d7c0c96480638280b66e1ff3b26210391480035ecfdb6b0562f607f58704941bc6f31403ae51e121642fc6bb4f84e64e9613c27d15ac2eThe 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.