App analysis · 20.10.2026
Privamatic
com.techtrest.privamatic · version 1.5.1
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)
- list of all installed apps —
android.permission.QUERY_ALL_PACKAGES - biometrics (fingerprint, face) —
android.permission.USE_BIOMETRIC - fingerprint —
android.permission.USE_FINGERPRINT
All manifest permissions (7)
android.permission.ACCESS_NETWORK_STATEandroid.permission.ACCESS_WIFI_STATEandroid.permission.QUERY_ALL_PACKAGESandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.USE_BIOMETRICandroid.permission.USE_FINGERPRINTcom.techtrest.privamatic.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
com.techtrest.privamatic · version 1.5.1 (code 9)ca82a832233fe4711be58e3e8b29a85fbfdfd2122ebbcf712048b9282d204dd54582016f7fc5ef35597bcf0f8b72ed93af02108e4a2fa58bf7b1509606ce67c7The 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.