App analysis · 20.10.2026
Fossify Clock Beta
org.fossify.clock · version 1.6.0
In short
SDKs found: 0. Companies: 0, of which outside the EEA — 0. Sensitive permissions: 1 — all code inside the app, including embedded SDKs, can use them.
Sensitive permissions (1)
- draw over other apps —
android.permission.SYSTEM_ALERT_WINDOW
All manifest permissions (12)
android.permission.FOREGROUND_SERVICEandroid.permission.FOREGROUND_SERVICE_SPECIAL_USEandroid.permission.POST_NOTIFICATIONSandroid.permission.RECEIVE_BOOT_COMPLETEDandroid.permission.SCHEDULE_EXACT_ALARMandroid.permission.SYSTEM_ALERT_WINDOWandroid.permission.USE_EXACT_ALARMandroid.permission.USE_FULL_SCREEN_INTENTandroid.permission.VIBRATEandroid.permission.WAKE_LOCKcom.android.alarm.permission.SET_ALARMorg.fossify.android.permission.WRITE_GLOBAL_SETTINGS
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
org.fossify.clock · version 1.6.0 (code 10)43cf9f0ec45f1f1ff2df47286622e5b8f3acedaeb07b7f7641b5243dbedca079affdb124d3f4720c2f98dbca9eacba0514fba4306e20a2786c861c3c0d6ff292The 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.