App analysis · 04.10.2026
cliQ
lk.etisalat.cloud.fwd.smpl · version 3.1.5
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)
- files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - draw over other apps —
android.permission.SYSTEM_ALERT_WINDOW
All manifest permissions (13)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.POST_NOTIFICATIONSandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.SCHEDULE_EXACT_ALARMandroid.permission.SYSTEM_ALERT_WINDOWandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.android.vending.CHECK_LICENSEcom.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICElk.etisalat.cloud.fwd.smpl.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
lk.etisalat.cloud.fwd.smpl · version 3.1.5 (code 661)980ce9605c90dc67f00ac58e0b36534f24dcd055a72a5d892e592f6cbb4189bac644eea62d9e08d256bd501fcb7eafd1e5b307ff75c35dd4e876d3be31f2f1622769b78c1753The 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.