URGEFLIP
Effective date: November 13, 2026
URGEFLIP helps you take a moment before opening apps you choose to protect.
We believe your digital wellbeing shouldn't come at the expense of your privacy.
This policy explains what information URGEFLIP uses, why we use it, and how you can stay in control.
URGEFLIP is operated by QWARTRIX SRL, Romania. For privacy questions, contact [email protected].
Your privacy at a glance
Your activity stays on your phone
Your protected apps, schedules, settings, and pause history are stored on your device. URGEFLIP doesn't send this history to our installation, purchase, or optional technical-reporting services.
We don't read your messages
URGEFLIP uses Android permissions to recognise app openings. It doesn't use them to read messages, passwords, or typed text.
You're in control of optional reporting
Mobile technical reporting is off by default. You can enable or disable it in Settings without losing access to protection or Supporter.
You can request data deletion
You can reset your local app history and request deletion of personal information held by our services, subject to applicable legal requirements.
1What information does URGEFLIP use?
Most of the information needed to use URGEFLIP stays on your device.
This includes:
- Apps you choose to protect.
- Your protection schedules and preferences.
- Your pause history and protection events.
- Onboarding progress and app settings.
- Your optional technical-reporting preferences.
We also store limited local information needed to check purchases and access to Supporter features.
You don't need to create an account.
URGEFLIP doesn't require an email address, username, or password to use the app.
However, optional online features use random installation and customer identifiers. These identifiers help us recognise your installation and manage access without requiring a personal login.
On a new Free installation, ordinary Free use does not register your installation with our API or automatically start RevenueCat.
When you request an online feature, such as Supporter, purchase restoration, review access, or Invite & Earn, limited information is exchanged with our services or providers.
An accountless experience does not necessarily mean anonymous online processing.
2How does app protection work?
To recognise when you open a protected app, URGEFLIP uses Android's Accessibility Service and Usage Access permissions.
Accessibility Service
This permission helps URGEFLIP detect app openings and display your pause screen at the right moment.
Android may provide information such as app package names, window information, and event timing. URGEFLIP processes these events locally to apply your protection rules.
Some events may relate to apps you haven't selected for protection before they are filtered.
Before you enable Accessibility, URGEFLIP shows a separate explanation of what information the service accesses and why. Choosing I agree opens Android Accessibility settings; it does not enable the permission. Choosing Not now returns to setup without granting access. You must enable the service separately in Android Settings.
URGEFLIP's Accessibility Service cannot retrieve screen contents or perform gestures. We don't use it to read messages, passwords, or typed text.
Usage Access
This helps URGEFLIP check recent app activity and improve the reliability of protection.
The app also checks which applications are available to launch so you can select the ones you want to protect.
You control these permissions.
You can change or revoke them in Android Settings. Some protection features won't work without the required permissions.
Force-stopping URGEFLIP or changing Android system settings may also interrupt protection.
Your protected-app selections and pause history are not sent as part of installation setup or optional technical reporting.
3Purchases and online services
URGEFLIP is free to download, with optional paid Supporter features.
We use two external services for purchases:
- Google Play processes Android purchases.
- RevenueCat helps manage subscriptions, one-time purchases, access status, and restoration.
When you open the Supporter screen, make a purchase, restore purchases, or request review access, the app may connect to our service and RevenueCat.
This can happen before you confirm a purchase.
Choosing to start Invite & Earn also uses our API, RevenueCat and Google Play verification to manage invitations and temporary Supporter rewards. See section G below.
Information exchanged may include random customer and installation identifiers, technical app information, purchase details, and access status.
RevenueCat may also be contacted to verify existing Supporter access or an unresolved purchase or access request. Once started, its SDK may remain active during that app session.
URGEFLIP doesn't ask you to enter payment-card information into the app itself.
Your purchase information is separate from your pause history.
Deleting local app data doesn't automatically cancel subscriptions or remove records held by Google Play or RevenueCat.
You can find more information in the Google Privacy Policy and RevenueCat Privacy Policy.
Temporary review access
Authorised reviewers can request temporary Supporter access using a review code.
A successful grant currently lasts 30 days. Reusing a code during an active grant doesn't extend that period.
Our service records the information needed to validate and manage the request. RevenueCat may receive the customer identifier and temporary entitlement information.
The entered review code is not stored in our application database.
4Optional technical reporting
We use technical information to understand and fix problems with URGEFLIP.
Mobile technical reporting is off by default.
If you choose to enable it, the app may send limited error reports and daily error counts to our reporting services.
These can include:
- App version and platform.
- Technical error codes and categories.
- Error severity.
- Random error-event identifiers.
- Daily counts of certain failures.
Reports help us investigate issues with app protection, schedules, pause screens, purchases, and restoration.
They don't include your messages, typed text, screen contents, protected-app selections, pause history, purchase receipts, or persistent customer identifier.
Automatic fatal-crash reporting is disabled in this Android version.
Network providers and reporting services may still process connection information, including IP addresses. Technical reports aren't necessarily completely anonymous.
Your choice
You can turn optional technical reporting on or off in Settings.
Turning it off stops further optional reporting and discards reports waiting to be sent from your device.
It doesn't automatically erase information already received, and it doesn't stop processing required for purchases, security, installation sessions, or website operation.
5How long do we keep information?
We keep information only for the purposes and periods described below, subject to applicable legal requirements.
| Information | How long it is kept |
|---|---|
| App settings and pause history | On your device until removed; no automatic app-defined expiry |
| Optional technical reports | Maximum 14 days under our application-telemetry policy |
| Designated telemetry operational logs | 13-day expiry policy |
| Installation and customer records | Reviewed every six months and retained while needed for access, restoration, security, or unresolved operations |
| Invitation attribution, reward and anti-abuse records | While needed to validate invitations, deliver or restore rewards, resolve requests or prevent repeat rewards; necessity reviewed every six months |
| Completed review-access records | Normally eligible for deletion after the applicable access and confirmation periods |
| Installation-linked privacy request references | While unresolved; minimal detached reference and resolution metadata for six calendar months after resolution, then removed through operator maintenance |
| Support emails and privacy requests | Six months after resolution, for copies under our control |
| Google Play and RevenueCat records | According to their applicable retention policies and agreements |
Some functional or provider records may need to be kept longer for active subscriptions, lifetime purchases, restoration, security, unresolved requests, or legal obligations. These separate retention criteria do not extend QWARTRIX’s 14-day application-telemetry policy.
A review date is not an automatic deletion date. Records that become eligible for deletion may also require a later maintenance operation.
Backups or records held independently by external providers follow their own applicable arrangements.
More information is available under Additional privacy details below.
6Your choices and data deletion
You're in control of your URGEFLIP experience.
Reset your app history
You can use the app's local reset feature to remove the settings and history covered by that reset.
Some installation identifiers and billing-access information are kept separately so existing access and restoration can continue working.
Clear Android app storage
You can remove the app's locally stored information through Android Settings.
This doesn't cancel subscriptions, issue refunds, or automatically erase information stored by external services.
Request deletion of online information
In Settings, choose Request data deletion. Opening this screen does not send a request.
If an existing verified installation session is available, you can choose Create request reference and then Email request. The app does not start RevenueCat or create a new installation or billing identity for this purpose. You decide whether to send the email.
If no usable session is available, you can still email [email protected] without a reference.
Creating a reference sends an authenticated request to QWARTRIX and stores the reference on your device. The reference helps us find the relevant installation records, but it does not prove your identity or authorise deletion by itself.
If the result is uncertain, the app can retry the same saved operation rather than creating a different request. Closing the screen does not undo a request already received by our service.
Creating a reference doesn't delete data, cancel a subscription, change Supporter access, or automatically send an email. You decide whether to contact us.
We may need limited information to verify your request, especially when purchases are involved.
Please don't send passwords, payment-card details, session credentials, review codes, or unnecessary sensitive information.
We assess deletion requests individually. Some information may need to be retained for legal obligations, security, purchase restoration, or unresolved operations.
Resetting local data or preparing a deletion email does not automatically erase remote records.
7Your rights and our responsibilities
QWARTRIX SRL is responsible for the personal-data processing described in this policy.
Where the General Data Protection Regulation (GDPR) applies, you may have the right to:
- Access your personal information.
- Correct inaccurate information.
- Request deletion.
- Restrict certain processing.
- Receive portable information where applicable.
- Object to processing based on legitimate interests.
- Withdraw consent for optional reporting.
These rights depend on the circumstances and applicable law.
Where GDPR applies, we respond without undue delay and normally within one month of receiving your request. If a permitted extension is needed because of the complexity or number of requests, we explain the reasons within the initial month.
You can exercise your rights by emailing [email protected].
You may also submit a complaint to a competent data-protection authority, including Romania's National Supervisory Authority for Personal Data Processing (ANSPDCP).
Why we process information
Under GDPR, we rely on the following legal bases:
Providing requested services — Article 6(1)(b)
To provide the protection functions and online services you request, including Supporter access, purchases, restoration, authorised review access, and invitations you choose to use, using the information necessary for those purposes.
Your consent — Article 6(1)(a)
For optional mobile technical reporting.
Legitimate interests — Article 6(1)(f)
To secure our services, authenticate requests, prevent abuse, operate and protect our website, respond to enquiries, and reconcile limited service records. Keeping the limited record of a resolved privacy request for six months supports our legitimate interest in demonstrating its handling and resolving follow-up questions.
Legal obligations — Article 6(1)(c)
To comply with applicable legal requirements, including data-protection duties.
You may object to processing based on legitimate interests. You can withdraw consent for optional reporting in Settings.
8Contact, security, and updates
Contact us
QWARTRIX SRL
Registered office: Str. Occidentului nr. 25D, parter, ap. 2
Popești-Leordeni, 077160, Romania
Privacy: [email protected]
Website: https://urgeflip.com
You can contact us with questions about your information, privacy rights, or how URGEFLIP works.
Security
We use safeguards such as HTTPS connections, Android private app storage, secure handling of session credentials, and restricted access to our services.
No digital service can guarantee absolute security.
Age requirements
URGEFLIP's initial release is intended for adults aged 18 and older.
This Android version does not verify age or provide a parental-consent process.
Changes to this policy
We may update this policy when our services, features, or data practices change.
The current version will be available at:
https://urgeflip.com/privacy-policy/
Significant changes will be communicated where required by law.
MORE DETAIL
Additional privacy details
The following information provides more detail about our services, providers, retention procedures, and processing arrangements.
It forms part of this Privacy Policy.
A. Installation identifiers and secure sessions
URGEFLIP uses a random customer identifier and a separate installation identifier for online Supporter and invitation functions.
When one of these functions is requested, our API at api.urgegap.com may establish an installation session and associate the identifiers.
The session credential is stored securely on your device. Our service stores a keyed hash of the credential and uses connection information, including IP-related information, to help secure requests and prevent abuse.
Existing identifiers and associations may be preserved across upgrades. An unresolved setup or access operation may be retried when needed for a requested online function.
An ordinary Free restart does not automatically resume a pending installation setup in the background. During a session in which an online function has been requested, incomplete setup may be retried.
Previously established Supporter access or unresolved billing checks may require online verification, including during startup.
These necessary online operations are independent of optional technical-reporting consent.
B. Service providers and international data transfers
We work with trusted service providers to operate URGEFLIP, process purchases, provide support, and keep our services secure.
- QWARTRIX SRL operates URGEFLIP's services and infrastructure in Romania.
- Google Play handles Android app distribution and purchases.
- RevenueCat manages purchases, subscriptions, and Supporter access.
- Cloudflare helps deliver and protect our website and online services.
- Hostico provides email services for support and privacy requests.
Some of these providers may process personal information outside the European Economic Area, including in the United States.
Where required, international transfers are protected by applicable legal safeguards, such as Standard Contractual Clauses. The safeguards and providers' legal responsibilities depend on the services involved.
You can find more information in our providers' privacy policies and data-processing agreements, or request details by emailing [email protected].
C. More about retention and deletion
Technical reporting
Our application-telemetry retention limit is 14 days for reports, daily counts, and derived hourly statistics.
Selective cleanup is scheduled earlier, at 13 days, to provide operational margin.
Designated operator-output records and telemetry alert records also have a 13-day expiry policy. Separate uptime and performance records have shorter one-day targets.
We monitor cleanup failures. A retention configuration doesn't by itself guarantee that a particular record has already been deleted.
We don't create backups of the application-telemetry databases. This statement doesn't cover backups independently maintained by external providers.
Installation and customer records
Functional records are reviewed every six calendar months, first from creation and subsequently from the last review.
We retain associations while needed for active or restorable purchases, installation sessions, security, unresolved operations, or related purposes.
For a Free installation, an operator removes the association through this review process only after verifying that the installation has been retired, its local association has been cleared, and no active access, purchase history, restorable purchase, unresolved request, or related record requires it. If this cannot be verified, the record is kept for a limited stated reason and reviewed again. Lack of recent API calls alone does not establish that an installation is unused. Minimal associations needed for Supporter, including lifetime access and restoration, are preserved while necessary.
Verified deletion requests are assessed separately rather than waiting for the next scheduled review.
Review-access records
Confirmed or closed-unused review-operation records normally become eligible for deletion 14 days after the later of access expiry and final confirmation or closure.
For an ordinary 30-day grant, this is typically about 44 days from the grant, plus any maintenance delay.
Records with uncertain outcomes may need to be kept for reconciliation. Reviewer-journal maintenance is not currently automatic, so eligibility doesn't guarantee immediate deletion.
Short-lived abuse-attempt records become eligible for removal after two hours, with execution potentially delayed.
Privacy request reference records
Unresolved reference records remain while the request needs handling. After an operator marks the request resolved, the record is detached from the customer and installation.
Minimal reference and resolution metadata are kept for six calendar months after resolution and are then removed through separate operator maintenance. Creating a reference does not erase customer or purchase data or change Supporter access.
Support correspondence
We retain support correspondence and privacy requests, including attachments and the minimal record of their resolution, for six months after the conversation or request is resolved.
This applies to copies under our control, including server mailboxes, email clients, sent and deleted-items folders, archives, and forwarded copies we control.
Copies held by email providers in their own recovery or backup systems follow the providers' separate arrangements. We do not claim that every internal provider backup is erased within the publicly stated email-recovery window.
External purchase records
RevenueCat's contractual retention arrangements and Google's data-retention policies apply separately.
Removing local app data or cancelling a subscription does not automatically erase these providers' records.
D. Privacy requests and identifying information
Your email address is not automatically associated with your random customer identifier.
For privacy requests, we use proportionate verification to locate relevant information and confirm authority.
A purchase transaction reference may help identify relevant records but doesn't, by itself, prove authority to access someone else's data.
Some technical reports aren't linked to customer identifiers. If we cannot identify information relating to a specific person, we will explain that limitation where possible.
We don't collect additional identifying information solely for identification when it isn't necessary for our processing.
No automatic remote-erasure operation is provided by the app.
E. Website visits and contact messages
When you visit our website, your browser sends information needed to request pages and assets.
Our website and security providers may process related connection information.
If you use our contact form, we receive the name, email address, topic, and message you submit. The form sends the message through Hostico to [email protected].
The form uses a hash of the submitted email address and temporary request counters to limit abuse. The request window is 15 minutes, and expired entries are cleared on a later request or process restart.
The form doesn't create its own persistent message database, but sent messages and provider copies are retained separately.
The Android technical-reporting preference doesn't control website visits or messages you choose to send.
F. Diagnostics and shared reports
The app's Help & diagnostics feature can create a local technical report.
This report is not automatically uploaded. If you choose to share it, Android passes it to the application or recipient you select.
Sharing a diagnostic report is separate from optional background technical reporting. Review the report and the selected recipient before sharing it.
G. Invite & Earn
Invite & Earn is optional. Ordinary Free use does not activate it. When you choose to start, we use the installation and customer identifiers needed for your invitation code, accepted attribution, verification and Supporter rewards. RevenueCat may start even if you do not buy anything. We do not upload your contacts or send invitations on your behalf.
New V2 invitations can give the inviter seven days of Supporter and the invited user three days after a qualifying new user accepts the code, completes setup, protects an app, completes a real Gap and passes verification. Earlier invitations keep the rules under which they were accepted; they do not receive a retroactive three-day reward.
The app sends limited confirmation events for setup, having a protected app and completing a Gap. These do not include the protected app's name, your list of apps, messages or pause history. A link or Google Play Install Referrer can prefill a code locally within a seven-day attribution window. A prefilled code is not accepted automatically.
Verification and prevention of repeat rewards
For invitation verification, we use Google Play Integrity to check the app, its Play licence and device integrity. Verification tokens and request hashes are used for this check, not as application telemetry. Short-lived challenge records expire after ten minutes and become eligible for cleanup after a further two-hour margin; maintenance runs hourly.
On Android 8 or later, starting Invite & Earn also derives an app-specific key from Android's identifier scoped to the app's signing key, Android user and device. The raw Android identifier is not sent to QWARTRIX. The app sends a one-way digest over HTTPS; our server protects it again with a private keyed hash and keeps the resulting minimal verification and reward-eligibility record. The digest is bound to the installation and a Google-verified request.
This prevents a new installation identity, reinstall or cleared app storage in the same Android profile from resetting invitation eligibility. It is not a universal device or personal identifier. Factory resets, different Android profiles and some platform changes can affect it; we do not claim to identify a person across those changes. We do not use Google's optional Device Recall service.
Records and your choices
We retain attribution, reward status, operation identifiers and the minimal anti-abuse receipt while needed to deliver or restore rewards, prevent repeat rewards or resolve an uncertain operation. These are functional records, distinct from optional technical reports and logs. Their necessity is reviewed every six calendar months; this is a review rule, not automatic deletion or permanent retention. A verified deletion request can be assessed sooner, including whether any limited security record remains necessary.
A local app reset does not revoke a reward or remove server-side eligibility records. You can use the deletion-request process in section 6 to ask us to assess these records. We do not put the raw Android identifier, verification token or installation credentials in the generated email.
Questions about your privacy?
We're here to help.
Your digital wellbeing. Your privacy. Your choice.