Privacy policy

Ruk

Android app com.crackoncloud.ruk, published by crackoncloud · Last updated 17 August 2026

1. What Ruk stores on your phone

Ruk keeps its records in the app's own private storage on your device. Nothing is uploaded and there is no copy of it anywhere else.

Your screen-time figures

• Daily foreground time and number of opens, per app
• Daily unlock count, longest session and an hour-of-day breakdown for the device

These come from Android's own usage statistics, read on the device (see §2).

Your configuration

• The apps and groups you chose to monitor
• Pause styles and durations, daily limits, schedules, focus sessions, saved session setups and their allow lists
• Feed-blocking rules, strict-mode state, theme and other settings

A record of your pauses

This is the most personal part of the database, and it exists so Ruk can show you what its pauses actually did for you:

• Which app was opened, when, which pause was shown, how long it lasted, and whether it ended in Continue or Not now
• Any intention you typed into a pause, the timeboxes you bought, and how you answered the exit review
• The reason you typed when spending an emergency exit during a focus session

Because it is the most intimate part of the record, an export leaves the raw log out unless you ask for it.

A health log for Ruk itself

When protection started, when the system stopped it, and when a permission was granted or revoked. This is what lets Ruk tell you honestly that it stopped working — for example after your phone's battery manager killed the service — instead of silently not protecting you. It is not analytics, and it never leaves the phone.

Backups and transfers

Ruk's database is deliberately excluded from Android's cloud backup, so it is never copied to Google's servers. It is kept on a direct device-to-device transfer, because that never leaves your hands. Uninstalling Ruk deletes all of it.

2. Permissions, and exactly what each one is for

Permission	What Ruk does with it
Usage access	Android holds the screen-time figures, and usage access is the only way an app can read them. This is what produces every number Ruk shows you.
Accessibility optional	Reports the package name and class name of the app coming to the foreground, so the pause can arrive before the content does. See the limits below.
Display over other apps	Draws the pause in front of the app you opened, for the duration of that pause only. Ruk never covers system UI and keeps no floating bubble on your screen.
Notifications	The ongoing protection notification Android requires, and a warning when a daily limit is nearly spent. Declining it costs the warning and nothing else.
Do Not Disturb access optional	Turns on Do Not Disturb and Android's device effects — greyscale, dimmed wallpaper — during a focus session, through a rule the system itself applies.
Run at startup	Restarts protection after a reboot or an app update, so it does not silently stop.
Foreground service	Keeps the detection loop alive while you have something to enforce, with an ongoing notification the whole time.
Biometric optional, off by default	Asks the system to confirm it is you before an emergency exit is spent. Ruk never enrols, reads or stores a fingerprint or face — the system answers yes or no.
App list	Ruk queries apps that have a launcher icon, so it can show you a list to choose from. It deliberately does not request the permission that reveals every installed package.

What the accessibility service reads — and what it never reads

If you grant it, Ruk's accessibility service is used for one purpose: to learn which app has just come to the foreground, so the pause you set up can appear before the feed loads.

• It reads window-state events, and uses only the package name and class name from them.
• If you turn on feed blocking, it additionally reads view identifiers, content descriptions and element class names — only while a feed surface is armed, and only inside the specific apps whose feeds you switched off.
• It never reads on-screen text, never captures or records the screen, and never logs keystrokes.
• These events are processed in memory and are never written to storage. What Ruk stores is your own record of your own pauses.

The service is never enabled quietly. A full-screen disclosure states all of the above before Android's accessibility settings are opened, and you can skip it: without accessibility access Ruk falls back to polling Android's usage statistics, which is slower and less accurate, and the app says so rather than pretending.

You can revoke accessibility or usage access in Android Settings at any time. Ruk reports the loss instead of quietly stopping.

3. Ruk Pro and Google Play

Ruk Pro is a single one-time purchase, never a subscription. The payment is handled entirely by Google Play: Ruk never sees, receives or stores your name, card, UPI ID or any other payment detail. Google tells the app only whether the Google account on the device owns the unlock.

Google's own handling of that purchase is covered by Google's privacy policy and the Google Play terms, not by this one. Ruk itself sends nothing, to Google or to anyone else, and there are no ads and no third-party analytics or advertising SDKs in the app.

4. What Ruk never does

• No account, no sign-up, no sync, no cloud profile
• No analytics, no crash reporting, no tracking or advertising identifiers
• No selling, sharing or disclosing of your data — there is nothing collected to sell
• No ads of any kind
• No reading of your messages, notifications, browsing or on-screen text
• No screenshots, screen recording, microphone or camera use
• No location access
• No device-admin control, and Ruk can always be uninstalled

5. Your control over the data

• Choose how long it is kept. The detailed record can be pruned to 30, 90 or 365 days, or kept forever. Ruk deletes to that window once a day.
• Export a copy. Settings → Your data writes a single JSON file to a location you pick, through Android's own file picker. The raw pause log is left out unless you include it.
• Delete everything. One action in Settings → Your data clears every record and resets the app's settings.
• Revoke any permission in Android Settings at any time.
• Uninstall. That removes all of it from the device, whatever any setting inside the app says. Because nothing was ever uploaded, there is no server-side copy to request the deletion of.

6. Children

Ruk is a self-control tool for its own user and is not directed at children under 13. It has no parental-control, monitoring or remote-management features, and it collects no personal information from anyone, of any age.

7. Changes to this policy

If Ruk ever changes what it stores or what it can read, this page changes with it and the date at the top is updated. The policy is kept deliberately identical to the privacy screen inside the app — a policy that claims more than the app does would be worth nothing.

8. Contact

Questions about this policy, or about anything Ruk stores: support@crackoncloud.com