zipt privacy policy

Effective from zipt 1.17.0 (previous version 6 October 2026, first version 9 September 2026) · Applies to the zipt Android app, package com.radheya.focusblocker, published by Radheya.

zipt collects no data unless you choose to sign in. Signing in is optional: every block works the same without it. If you sign in with Google, we keep your name, email address and a user id so the account can be used for community features later. zipt has no analytics and no advertising, and nothing you do on your phone, and nothing zipt's accessibility service sees, is ever sent anywhere. This page exists because zipt uses two Android permissions that deserve a plain explanation.

What zipt is

zipt turns your phone calls-only for a block of time you choose, or on a daily schedule. During a block, only the apps you allowed stay reachable. A block can be ended early only with a code from a person you chose: one of ten one-time codes you handed them at setup, or a six-digit code from an authenticator app on their phone. Without codes, every block runs to the time you set, unless you chose the wait in Settings: then End early starts a wait that grows with each use. Calls, including emergency calls, always work.

Permissions, and exactly what each one sees

PermissionWhat zipt does with itWhat it can see
Accessibility service During a block, notices when a different app comes to the front and brings the lock screen back. The package name of the app that came to the front, and nothing else. The service is configured so it cannot read screen content (canRetrieveWindowContent="false"). The name is compared against your allow-list and discarded; it is not stored.
Display over other apps Lets a background service open the lock screen. zipt never draws anything on top of another app. Nothing.
Alarms & reminders Starts and ends blocks at the exact minute. Nothing.
Notifications A heads-up before a scheduled block and a notice when one ends. Nothing.
Device admin (optional) Makes uninstalling zipt a two-step job. The admin declares no policies: it cannot lock the phone, wipe it, or change a password. Nothing.
Battery optimisation exemption (optional) Stops the system pausing a running block. Nothing.

What is stored on your phone

All of it is excluded from Android backup and device-to-device transfer. Uninstalling zipt deletes all of it.

Usage report

zipt keeps simple counts on your phone: which setup steps you reached, which permissions are on, how many blocks you started and how each ended, how many schedules are on, and the date of the app's last crash or freeze if Android recorded one. You can read them in Settings under Usage report. They contain no app names, no unlock codes and nothing zipt saw on your screen. If you tap Share report, Android's share sheet opens with that text and you choose the app and the recipient; nothing is sent unless you send it. If you send it to us, we use it only to fix and improve zipt, and delete it within 90 days. The counts are deleted when you uninstall zipt.

Optional account

In Settings, under Account, you can sign in with your Google account. Google shows its own sheet and tells you what it shares: your name, email address and profile picture link. We keep the name, the email address and a user id created by Firebase Authentication, a Google service that holds them for Radheya on Google's servers. We use them only to run your zipt account and, when those features exist, to show your name in community and leaderboards you choose to join. We do not sell them, use them for advertising or share them with anyone else. Sign in is not possible during a block.

You can sign out at any time, and Delete account in the same card removes the account and everything Radheya holds for it at once. If you no longer have the app, email hello@radheya.in from the same address and we delete it within 7 days. For a complaint about how we handle your data, write to the same address; we reply within 7 days.

What leaves your phone

Signed out: nothing. zipt declares the INTERNET permission only for the optional sign-in, and nothing uses it until you tap Sign in with Google. Signed in: the sign-in itself, between your phone, Google and Firebase. Your blocks, schedules, codes, the activity log, the usage report and anything the accessibility service sees stay on the phone.

Accessibility service, in full

Google Play asks apps that use Android's accessibility service to say exactly what they do with it. zipt's service subscribes to one event, "a window changed state", and reads one field of it, the package name of the app now in front. It does this only while a block you started is running; outside a block the service receives the event and returns at once. It is declared without the ability to retrieve window content, so it cannot read text, fields, passwords or anything else on the screen, and nothing it sees is stored or transmitted. It is not an accessibility tool for people with disabilities and does not claim to be one. You are asked for this permission on a screen inside the app that says all of this, with a Grant button and a Not now button, before Android's own dialog appears.

Children

zipt is not directed at children. Accounts are for people 18 and over.

Changes

If a future version sends anything more off the phone, this page and the app will say so in plain words first, and the change will be opt-in. 1.17.0 added the optional account above.

Contact

Radheya · hello@radheya.in · zipt.radheya.in · Terms of use