App analysis · 17.10.2026
Prisma3D Legacy
com.prisma3D.prisma3DLegacy · version 2.1.2
In short
SDKs found: 3. Companies: 1, of which outside the EEA — 1. Sensitive permissions: 5 — all code inside the app, including embedded SDKs, can use them.
What is inside — embedded SDKs
- Google AdMob — Google LLC, United States outside EEA advertising
- Google Firebase Analytics — Google LLC, United States outside EEA analytics
- Google User Messaging Platform — Google LLC, United States outside EEA consent platform
Sensitive permissions (5)
- camera —
android.permission.CAMERA - files on the device —
android.permission.READ_EXTERNAL_STORAGE - microphone —
android.permission.RECORD_AUDIO - write files on the device —
android.permission.WRITE_EXTERNAL_STORAGE - advertising ID —
com.google.android.gms.permission.AD_ID
All manifest permissions (11)
android.permission.ACCESS_NETWORK_STATEandroid.permission.CAMERAandroid.permission.FOREGROUND_SERVICEandroid.permission.INTERNETandroid.permission.READ_EXTERNAL_STORAGEandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.RECORD_AUDIOandroid.permission.VIBRATEandroid.permission.WAKE_LOCKandroid.permission.WRITE_EXTERNAL_STORAGEcom.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.prisma3D.prisma3DLegacy · version 2.1.2 (code 81)391261fe219e3a4a88044a6971681d7944096f14cf151d8faa9827ada4166218f899d597c89fbe65c9db782b94758425e11f9037b1cdba1b53f21469fd2aca9613c27d15ac2eThe 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.