PRIVACY POLICY
Your privacy
matters.
Clear information about the app, your data, and your choices.
Last updated: 1 November 2026
Your selected apps and pause history are stored locally. Referral and purchase features involve separate identifiers and external services when enabled.
1. Overview
URGEFLIP is the website brand for URGEGAP. This policy refers to the Android app as URGEGAP. URGEGAP helps you pause when opening apps you choose. This policy explains the Android app’s local data, permission-dependent protection, and referral and purchase features. Using the app does not require a traditional account. The app uses separate random customer and installation identifiers; accountless use does not mean that no identifiers exist or that all data stays on your device.
Careful handling
Understand local and external data.
Your choices
Manage selections and access.
Clear limits
External services are described.
Transparency
Know what local deletion removes.
2. On-device data
URGEGAP stores selected apps and their labels, protection settings including schedules and Focus Modes, pause events, protection checks, and local diagnostics on your device. Pause history supports insights into choices such as continuing or stepping away. Local product data can include recovery copies used to preserve settings and history. These records are distinct from identifiers, purchase associations, and referral records processed by external services.
Selected apps
Settings
Pause historyDiagnostics3. Android permissions
Android Accessibility access provides the package name of the app that comes to the foreground. URGEGAP compares it with your selected apps and can present the Gap. This service does not retrieve screen contents, messages, passwords, or typed text, and cannot perform gestures. Usage Access supports related protection checks. You can revoke access in Android settings; functions that depend on that access stop working. Protection depends on permissions and device behavior and does not guarantee interception before any app content appears.
4. External services
When referrals are enabled, the referral service processes random customer and installation identifiers, invite attribution, activation events and timestamps, reward status, and claim-attempt information. Registration abuse limits use a hash derived from the connection IP address. RevenueCat can receive a pseudonymous customer identifier and purchase or reward association to determine Supporter access. Referral requests do not include protected-app names, contacts, messages, or detailed pause history. Sharing an invitation uses your phone’s native share sheet. Store purchases are also subject to the store’s own data practices.
5. Your controls and deletion
Choose and change protected apps and settings in the app, and manage permissions in Android settings. Delete local data resets selected apps, pause history, and diagnostics, but keeps separate customer and installation identifiers, the invite session, and the purchase association. Clearing URGEGAP’s app storage in Android settings removes local identifiers and the session token. Neither action deletes referral records already stored on the server or erases store purchase records. Local deletion is therefore not a request to erase every external record. Use the Contact page for privacy and data-handling questions, including requests concerning records held outside your device.
6. Retention and website information
Local product records remain on your device until you reset them or remove app storage. External referral, purchase, and support records are separate from that local history. The referral implementation removes transient registration and claim-attempt records older than two hours at startup and during hourly cleanup; that schedule does not describe retention of other referral records. When you visit this website, your browser sends the information needed to request its pages and assets. When you use the contact form, your name, email address, selected topic, and message are sent through our email provider to our support mailbox so we can handle your request. Sending a message does not guarantee an immediate response. Website delivery and support correspondence are separate from the app’s local pause history. Do not include passwords, payment details, or private message contents in support correspondence.
7. Privacy questions
Visit the Contact page for privacy and support options, or email [email protected] with privacy and data-handling questions. The FAQ explains app protection and permissions. Keep app permissions and local deletion choices separate from requests about external records. The date above identifies the latest update to this text.
Privacy and support options →