App analysis · 10.10.2026
MyGov
in.mygov.mobile · version 2.8.3
In short
SDKs found: 2. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 4 — 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
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
Sensitive permissions (4)
- camera —
android.permission.CAMERA - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - access credentials —
android.permission.USE_CREDENTIALS - fingerprint —
android.permission.USE_FINGERPRINT
All manifest permissions (11)
android.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.USE_BIOMETRICandroid.permission.USE_CREDENTIALSandroid.permission.USE_FINGERPRINTandroid.permission.WAKE_LOCKcom.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
in.mygov.mobile · version 2.8.3 (code 341)cd36fd4cd489a7a9db5be9a4ddb5070d4c6bc436e99e0de5ce394eb17d4542ff906f9cfc9100db748d79638e1780430ff5d10a67eb7a6c78e5e430289965f7512769b78c1753The 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.