App analysis · 18.10.2026
Visible Body Suite
com.visiblebody.subscription · version 5.05.022
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
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
Sensitive permissions (4)
- camera —
android.permission.CAMERA - files on the device —
android.permission.READ_EXTERNAL_STORAGE - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (15)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_DATA_SYNCandroid.permission.INTERNETandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.READ_INTERNAL_STORAGEandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEandroid.permission.WRITE_INTERNAL_STORAGEcom.android.vending.BILLINGcom.android.vending.CHECK_LICENSEcom.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
com.visiblebody.subscription · version 5.05.022 (code 668)73677f985eb676f44a212b1cc81667b64201677298b863737a00c2bfcddb2058e43a8944d8839d1a8cf452534e45bb6a58c4ec5c798a1e4310a52e58cf4ae34e13c27d15ac2eThe 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.