App analysis · 09.10.2026
Omniva
ee.post.android · version 2017.02.01.r26
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 3 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (3)
- approximate location —
android.permission.ACCESS_COARSE_LOCATION - precise location —
android.permission.ACCESS_FINE_LOCATION - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE
All manifest permissions (5)
android.permission.ACCESS_COARSE_LOCATIONandroid.permission.ACCESS_FINE_LOCATIONandroid.permission.ACCESS_NETWORK_STATEandroid.permission.INTERNETandroid.permission.WRITE_EXTERNAL_STORAGE
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
ee.post.android · version 2017.02.01.r26 (code 26)4648f691b8df7e7b450d7a0e1446918b5519caadd372cc76f740c4298e3108f888a04b47a7c10372be40bc52ae93bb29d335d4afe498e97de3756d8853aeffa72769b78c1753The 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.