App analysis · 14.10.2026
m10
com.m10 · version 1.470.0
Session recording is possible
Sentry ships with a screen-and-tap recording module. It comes with the SDK by default and is switched on by the developer's settings, which are not visible in the code. The capability is there.
In short
SDKs found: 7. Companies: 3, of which outside the EEA — 3. Sensitive permissions: 13 — 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 Remote Config / A/B Testing — Google LLC, United States outside EEA удалённая настройка / A/B-тесты
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google reCAPTCHA — Google LLC, United States outside EEA защита от ботов
- AppsFlyer — AppsFlyer Ltd, Israel outside EEA атрибуция установок
- Sentry — Functional Software Inc., United States outside EEA crash reporting
Sensitive permissions (13)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - contacts —
android.permission.READ_CONTACTS - modify contacts —
android.permission.WRITE_CONTACTS - camera —
android.permission.CAMERA - microphone —
android.permission.RECORD_AUDIO - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - NFC: reading cards, documents and tags —
android.permission.NFC - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE - 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 - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (28)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CAMERAandroid.permission.INTERNETandroid.permission.MODIFY_AUDIO_SETTINGSandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_CONTACTSandroid.permission.READ_PHONE_STATEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.RECORD_AUDIOandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_CONTACTSandroid.permission.WRITE_EMBEDDED_SUBSCRIPTIONSandroid.permission.WRITE_EXTERNAL_STORAGEcom.google.android.c2dm.permission.RECEIVEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICEcom.google.android.gms.permission.AD_IDcom.google.android.providers.gsf.permission.READ_GSERVICEScom.huawei.appmarket.service.commondata.permission.GET_COMMON_DATAcom.m10.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONcom.samsung.android.mapsagent.permission.READ_APP_INFO
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.m10 · version 1.470.0 (code 1790768528)e2fc2723633c3d18176b77850056e6276adc5fdc88dde5d6e686f2ee2174c78a37e6bcd1360b00d978dfa99f11d0c792899353d7e1a5d68e6a36869080cd760313c27d15ac2eThe 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.