App analysis · 11.10.2026
Jobat
be.jobat.mobile · version 2.5.4
Records your screen and taps
Inside: Microsoft Clarity — a session-recording service. Such SDKs record where you tap, how you scroll and what is on the screen, and send it to the SDK company for analysis. What exactly gets into the recording is decided by the app.
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: 10. Companies: 6, of which outside the EEA — 5. Sensitive permissions: 12 — 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
- Meta (Facebook) Login / Share — Meta Platforms, United States outside EEA social login
- Meta (Facebook) SDK — Meta Platforms, United States outside EEA advertising / analytics
- Airship — Airship, United States outside EEA маркетинг / push
- Didomi — Didomi, France EEA consent platform
- Sentry — Functional Software Inc., United States outside EEA crash reporting
- Microsoft Clarity — Microsoft, United States outside EEA запись сеансов
Sensitive permissions (12)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - accounts on the device —
android.permission.GET_ACCOUNTS - camera —
android.permission.CAMERA - files on the device —
android.permission.READ_EXTERNAL_STORAGE - microphone —
android.permission.RECORD_AUDIO - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - 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 (23)
android.permission.ACCESS_ADSERVICES_AD_IDandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONandroid.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.GET_ACCOUNTSandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.RECORD_AUDIOandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEbe.jobat.mobile.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONbe.jobat.mobile.permission.UA_DATAcom.google.android.c2dm.permission.RECEIVEcom.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
be.jobat.mobile · version 2.5.4 (code 189)3c74fa84ac3198e9d7b7d5bec203faf3902e0d9b372e61b0d03467535b3959f4b15a024cae985cea0aad95063123a9ca3f65863541031a9b59e574103696331d2769b78c1753The 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.