App analysis · 18.10.2026
Saudi Visa Bio
sa.gov.mofa.saudivisabio · version 2.8.2
In short
SDKs found: 1. 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
- Microsoft App Center — Microsoft, United States outside EEA analytics / crash reporting
Sensitive permissions (4)
- camera —
android.permission.CAMERA - NFC: reading cards, documents and tags —
android.permission.NFC - phone data (carrier, call state) —
android.permission.READ_PHONE_STATE - fingerprint —
android.permission.USE_FINGERPRINT
All manifest permissions (16)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CAMERAandroid.permission.CHANGE_NETWORK_STATEandroid.permission.CHANGE_WIFI_STATEandroid.permission.FLASHLIGHTandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.NFCandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_PHONE_STATEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.USE_FINGERPRINTandroid.permission.WAKE_LOCKcom.google.android.c2dm.permission.RECEIVEsa.gov.mofa.saudivisabio.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
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
sa.gov.mofa.saudivisabio · version 2.8.2 (code 15810)27eb442028381d0ddbf3ad3b480439bd766da99783f775930621531455c3e9b39019f5a839d82c9299b8b2327e6c60ff41da9cb618c02021906e230f9752e17c13c27d15ac2eThe 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.