App analysis · 07.10.2026

Pilet.ee

ee.ut.ridango.android.pilet · version 1.9.2

0SDKs found

0companies

0companies outside the EEA

2sensitive permissions

In short

SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 2 — all code inside the app, including embedded SDKs, can use them.

Sensitive permissions (2)

approximate location — android.permission.ACCESS_COARSE_LOCATION
precise location — android.permission.ACCESS_FINE_LOCATION

All manifest permissions (5)

android.permission.ACCESS_COARSE_LOCATION
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_NETWORK_STATE
android.permission.INTERNET
com.google.android.providers.gsf.permission.READ_GSERVICES

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

File: Pilet.ee_1.9.2_APKPure.apk (5.1 MB)

Package: ee.ut.ridango.android.pilet · version 1.9.2 (code 2016122923)

Android: minimum API 16, target API 28

File SHA-256: e1d5ee38b78d6e79fdab506a870b9f9b4ac878d9daebb8a981687d7bb0598466

Developer signature (SHA-256): 6c4b8cf262b2784870a183d8698fc16c9f05fe71e29b32cf0b8ad7020d359d0d

Library: 63 SDK · 81 permissions · 2769b78c1753

File source: APKPure

The 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.

Download card (Markdown)

← All analysed apps · Check your own app