Last updated: November 2, 2026 ยท Developer: SGKSLabs (sgkslabs.in)
UNHOOK is designed to work entirely on your device. It has no server, no account system, and no third-party advertising or analytics SDKs. This policy explains exactly what the app accesses, why, and what it never does.
What UNHOOK does not do
- No account creation, login, or sign-in of any kind.
- No cloud storage or cloud synchronization. There is no UNHOOK server.
- No advertising SDKs.
- No analytics or crash-reporting SDKs that transmit data off the device.
- No
INTERNETpermission is declared in the app at all — UNHOOK cannot make a network request even if it tried to. - No collection of notification content, message text, or screen content.
- No keystroke logging of any kind.
What UNHOOK accesses, and why
Usage Access
Used to read on-device, aggregate screen-time and app-usage statistics so the Home and Insights screens can show your real screen time and most-used apps, and to detect when you open an application you've chosen to restrict, so UNHOOK can show its intervention ("blocking") screen. This data is read, displayed, and stored only in the local database on your device. It is never uploaded anywhere.
- Restricted-app detection works by periodically checking which app is currently in the foreground — UNHOOK deliberately does not use an Accessibility Service for this, because many banking and payment apps refuse to run, or show a fraud warning, the moment any Accessibility Service is enabled on the device at all, regardless of what it does.
- This never reads on-screen text, form fields, passwords, or any other screen content, and never captures keystrokes — it only ever learns the package name of the app currently in the foreground.
Notification Access
Used only to suppress notifications from applications you've chosen to restrict, while protection is active. UNHOOK:
- Reads only the package name of an incoming notification to decide whether to cancel it.
- Never reads, logs, or stores a notification's title, text, or any other content.
- Stores only a per-app, per-day count of how many notifications were suppressed, for the Insights screen.
- Immediately stops suppressing notifications for an app the moment it is unrestricted or protection is turned off.
Boot completion
Used only to re-run light local housekeeping (clearing expired temporary unlocks, refreshing the day's screen-time snapshot) shortly after the device restarts.
Notifications (Android 13+)
Used only to show you local notifications you'd expect — e.g. "your temporary unlock just ended." These notifications are generated on-device and never involve a push-notification server.
"Protection is active" notification
While protection is turned on, Android requires UNHOOK to show a persistent, low-priority notification for the background service that watches for restricted-app launches. It carries no personal data — just a static "UNHOOK protection is active" message — and disappears the moment you turn protection off.
Data storage
All data UNHOOK creates — your restricted-app list, unlock history, screen-time snapshots, and settings — is stored locally on your device only. It is not backed up to the cloud, and is deleted completely if you uninstall the app, or immediately if you use Settings → Clear application data inside UNHOOK.
Optional PIN
If you choose to set a PIN to protect UNHOOK's settings from casual changes, the PIN itself is never stored. Only a salted, iterated cryptographic hash of it is stored locally — the original PIN cannot be recovered from that hash.
Children's privacy
UNHOOK does not knowingly collect data from anyone, of any age, because it does not collect data off-device at all.
Changes to this policy
If UNHOOK's data practices ever change, this page will be updated and the "Last updated" date revised accordingly, before such a change ships.
Contact
Questions about this policy can be directed to SGKSLabs via sgkslabs.in or support@sgkslabs.in.