Privacy Policy
LoopBreak Privacy Policy
This Privacy Policy explains what information LoopBreak uses, what it does not collect, and how local storage, optional cloud backup, recovery, statistics, Accessibility Service, and Google Play subscriptions are handled.
Last updated: August 1, 2026
1. Overview
LoopBreak is a sleep-focused app-blocking tool. It helps users block selected apps during recurring schedules, Quick Lock sessions, and other user-enabled protected states. It can allow limited temporary access through QR codes or NFC tags.
LoopBreak is designed to avoid collecting personal content. The app does not read your messages, passwords, typed text, financial information, photos, contacts, emails, or the private content you view inside other apps.
2. LoopBreak ID
LoopBreak creates a random anonymous LoopBreak ID. This ID is not based on your name, email address, phone number, device serial number, or Google account.
The LoopBreak ID is used to associate app settings, unlock limits, optional backup data, statistics, and recovery information with LoopBreak. If you restore an existing LoopBreak ID on another installation, eligible backed-up information may be restored to that installation.
3. Information stored on your device
LoopBreak stores information locally so the app can operate. Depending on the features you use, this may include selected blocked apps, recurring schedules, profiles, presets, Quick Lock settings, unlock counters, NFC tag assignments, Strict Lockdown and Mindful Delay preferences, statistics, app-time records, backup status, and changes waiting to be backed up.
Local information remains on the device unless a feature requires cloud communication or you enable an available cloud-backup option.
4. Optional cloud backup and recovery
LoopBreak can back up eligible information to Flash Finds' cloud service and associate it with your anonymous LoopBreak ID. Depending on the options you enable, backed-up information may include settings and preferences, recurring schedules, profiles, presets, selected blocked-app package names, statistics and unlock-event records, and unlocked app-time history.
Categories presented as optional are uploaded only when you enable them. LoopBreak is designed to remain local-first, so pending changes may be kept on the device until a backup can complete.
LoopBreak normally groups pending settings, schedules, statistics events, and enabled app-time history into combined backup uploads, generally after 9 p.m. when changes are waiting. An upload may occur earlier when the pending queue becomes large or information has remained pending for more than 24 hours. If the device is offline, LoopBreak keeps the information queued locally and tries again later. A manual Back up now option may also be available, subject to a short cooldown.
Restoring a LoopBreak ID restores eligible LoopBreak settings and backup data. It does not restore or create a Google Play subscription.
5. Statistics and unlock activity
LoopBreak may record activity related to app blocking and temporary unlocks. This may include the unlock method, unlock tier, unlock duration, blocked attempts or unsuccessful unlock attempts, whether an unlock occurred during a protected state, scheduled and protected time, and related counters used by the Stats screen.
This information is used to provide in-app Stats, enforce unlock limits, restore enabled backup data, diagnose problems, and improve app reliability. It is not used to identify the content you view, type, read, or send inside other apps.
6. Unlocked App Time
When Unlocked App Time is enabled, LoopBreak may record the package name of a selected app and the amount of time it was active during a temporary QR or NFC unlock. This information is used to create the Unlocked App Time section of Stats.
LoopBreak does not record what you viewed, typed, read, posted, or did inside the selected app. Cloud backup of unlocked app-time history is optional.
7. Cloud configuration and service availability
LoopBreak may connect to Flash Finds' services to download current app configuration, including available unlock tiers and unlock limits, and to support enabled backup and recovery features.
If the cloud service is temporarily unavailable, LoopBreak may continue using information already saved on the device and try again later.
8. Accessibility Service
LoopBreak uses Android Accessibility Service to detect selected app openings and operate the app-blocking controls you configure during recurring schedules, Quick Lock sessions, and other active protected states. While protection is active, it may also detect relevant Android settings screens that could disable or weaken LoopBreak and show a warning before continuing.
LoopBreak does not use Accessibility Service to read messages, passwords, typed text, financial information, or private screen content from other apps.
For more details, read the LoopBreak Accessibility explanation.
9. Camera and QR scanning
LoopBreak may use the device camera to scan QR codes for temporary unlock access. Camera access is used only for QR scanning inside the app.
LoopBreak does not use the camera to record video, save photos, or identify people.
10. NFC tags
LoopBreak may read the identifier of an NFC tag that you choose to set up for unlock access. The app uses that identifier to recognize the configured unlock action or tier.
LoopBreak does not need to permanently write personal information to NFC tags.
11. Google Play subscriptions
LoopBreak Premium subscriptions are purchased and managed through Google Play. Google processes the payment and provides LoopBreak with purchase-status information needed to determine whether Premium is active. Flash Finds does not receive your complete payment-card number.
Google's handling of payment and account information is governed by Google's own privacy policies and terms. Restoring purchases restores an eligible Google Play Premium entitlement; it is separate from restoring a LoopBreak ID and its eligible backup data.
12. Information LoopBreak does not collect
LoopBreak does not collect or read:
- Messages or chat content
- Passwords or typed text
- Complete payment-card information
- Banking or financial account content
- Photos or videos from your device
- Contacts
- Emails
- Private screen content from other apps
- Precise GPS location
13. Service providers and data sharing
LoopBreak does not sell user data and does not use advertising tracking.
Limited app information may be processed by service providers only as needed to operate LoopBreak. These providers may include Cloudflare for application hosting, configuration, and cloud-backup infrastructure, and Google Play for app distribution, subscriptions, and purchase-status verification.
Information may also be disclosed when required by law, to protect users or the service, or as part of a business transfer, subject to applicable legal requirements.
14. Children
LoopBreak is not designed for children under 13. The app is intended for users who want to manage their own app usage and sleep-time phone habits.
15. Removing app data
You can remove locally stored LoopBreak data by uninstalling the app or clearing its app data in Android settings. Doing so removes the local copy from that device but does not necessarily remove information already included in cloud backup.
To request deletion of cloud data associated with a LoopBreak ID, use the instructions on the Data Deletion page or contact support and include the LoopBreak ID shown in the app. Keep in mind that deleting cloud backup does not cancel a Google Play subscription, and cancelling a subscription does not automatically delete LoopBreak cloud backup.
Google may retain subscription and payment records under its own legal obligations and policies.
Support: [email protected]
16. Security and retention
Flash Finds uses reasonable technical and organizational measures intended to protect information handled by LoopBreak. No storage or transmission method can be guaranteed to be completely secure.
Information is retained only for as long as reasonably needed to provide the service, maintain backups and recovery, meet legal obligations, resolve disputes, and protect LoopBreak. Specific retention periods may vary by data type and operational need.
17. Changes to this policy
This Privacy Policy may be updated from time to time as LoopBreak changes. Updates will be posted on this page with a revised Last updated date.
18. Contact
For privacy questions or support, contact: