What PullBack does and doesn't do with your data.

PullBack is a single-purpose Android app that interrupts selected apps after a timer and returns you to your home screen. This policy describes what PullBack V2 accesses, what stays on your device, and what is sent only when you choose a network feature.

Core timing and pull-back features work without an account. Optional Google sign-in supports account-based offers, referrals, eligibility checks and purchase verification where those features are available. Trial terms and eligibility are shown in the app before you choose to start an offer.

1. Plain-English summary

• Core features work without an account. Optional Google sign-in enables eligible users to choose an account-based 14-day trial and supports referrals and purchase verification. Offer availability and eligibility are shown in the app. Selected app names and detailed timer records stay on your device. If you apply a referral and opt in to qualification timing, account-linked session start and finish times are sent without app names or screen content. PullBack has no ads or advertising SDK.
• PullBack does not read what is on your screen. It does not capture screenshots, messages, posts, captions, search history, form fields, passwords, keystrokes, or other in-app content.
• PullBack uses Android's AccessibilityService API to detect the foreground package name and window-change events for apps you chose to limit. It also checks limited window metadata to distinguish picture-in-picture windows.
• Selected app names and screen content stay on your device. Foreground detection supports timing, session recovery, stats and PullBack's interruption feature. Account-linked session timing is sent only after referral participation is enabled.
• Network use is limited and user-directed. Google Play handles purchases. A code you choose to redeem is sent to PullBack's redemption service. A bug report or feature request is sent only after you fill it out and tap Submit. Optional Google sign-in also connects to our account service for trials, referrals, eligibility checks and purchase verification.

If that summary is enough for you, you can stop reading here. The sections below explain the same ideas in more detail.

---

2. What data PullBack accesses on your device

PullBack reads the following while it is running:

PullBack does not access:

• The content of any app you open (no screenshots, no screen recording, no text scraping).
• Your messages, calls, contacts, device photo library, microphone, camera, or location.
• Your accounts on TikTok, Instagram, YouTube, Facebook, Snapchat, Reddit, X, Threads, or any other service. PullBack never logs into anything on your behalf.
• Browsing history.
• Advertising IDs. For optional account eligibility checks, PullBack sends an app-specific hashed device value; the server stores a further keyed hash.

3. Data sent off-device

PullBack does not include advertising or automatic crash-reporting SDKs. Selected app names and screen content are not sent off-device.

• Google Play purchases. Google Play processes subscription and lifetime purchases. Where account features are enabled, PullBack's service can verify purchase tokens with Google and stores encrypted purchase references, product and subscription status, and reward records. PullBack does not receive card details.
• Pro code redemption. If you enter and submit a 16-character Pro code, that code is sent to PullBack's redemption endpoint to validate it.
• Bug reports and feature requests. If you tap Submit, PullBack sends the text you entered plus app version, Android version, device model, enabled-app count, timer setting, service state, and local progress counters. The form tells you this before submission.
• Standard connection information, such as an IP address, may be processed by Google Play, the account service or hosting providers when handling network requests. The account service also uses keyed IP-derived values for rate limiting.
• We do not include advertising SDKs.
• We do not share data with any third party for advertising or marketing purposes.

Optional Google sign-in, trials and referrals

Where account features are enabled, PullBack uses a shared Supabase Auth service to verify Google sign-in. It processes the account identifier, email address, and available name and profile image supplied by Google. The account service stores app-specific protected identifiers derived from your Google identity and device for eligibility checks. Google Play Integrity verifies app and device eligibility. Integrity tokens are not retained.

Eligible users can choose to start an offered 14-day Pro trial after Google sign-in. No payment method is required and this account trial does not charge automatically or start a paid subscription. The account service stores trial start and expiry information to enforce eligibility. Availability and offer terms are shown in the app before you start.

If you apply a referral and opt in to qualification timing, PullBack sends account-linked session start and finish times. You can turn this off in Settings > Account > Referrals. It does not send selected app names, messages or screen content for this purpose. Qualification requires three completed sessions of at least 60 seconds and no more than four hours, on at least two UTC calendar days, with the first and last session starts at least 20 hours apart. These records are not anonymous analytics.

4. Permissions and why each one exists

PullBack presents one required system service and one optional runtime permission during setup. Each is used solely for the purpose described.

• Accessibility service. Required for foreground-app detection, session timing, the pull-back screen, and Android's Home action when a timer ends. PullBack shows a prominent disclosure with Agree and Not now choices before opening Android's Accessibility settings.
• Notifications (POST_NOTIFICATIONS). Optional. Used for save confirmations and timer status.
• Internet and network state. Used for Google Play billing, optional account authentication, eligibility and referral timing, a Pro code you submit, and feedback you submit.

You can revoke any of these permissions in Android Settings at any time. Doing so will reduce or disable PullBack's functionality, but will not affect your privacy.

5. Where data is stored

PullBack settings and progress are stored locally using Android DataStore. Session and diagnostic events are stored locally using a Room database. There is no cloud sync for these local records. PullBack disables Android backup for its app storage, so local records are not included in Android backup and restore.

Uninstalling removes the app's local storage. Shared account, referral, trial and purchase records remain on the server until they are handled through the account deletion process. Account credentials and access caches are encrypted locally and excluded from Android backup.

6. Children

PullBack is not directed at children under 13 and is a self-management tool, not a parental control product. We do not knowingly solicit personal information from children.

7. Request account and data deletion

If you have a PullBack account, open Settings > Account > Delete account > Request account deletion. You can also request PullBack account deletion in your browser. Sign in with the Google account used for PullBack, review the scope and submit. The privacy contact form is available for help verifying ownership. Never send passwords, payment card details or identity documents.

An in-app request immediately disables shared trial and referral access and returns a pending request reference. Pending means the request has been received, not that erasure is complete. Check the account section or contact support for progress. This request covers your PullBack account; it does not delete your ToddlerLock, Unburden or Google accounts. The shared login remains while another app account needs it. Account deletion does not cancel a Google Play subscription. Manage PullBack subscriptions in Google Play to stop future renewals.

Some limited app-specific eligibility, purchase and reward evidence may be retained to prevent repeated trials, duplicate rewards and purchase theft. The retained evidence does not include selected app names or screen content. Google Play and other providers may retain their own transaction records under their policies.

Most PullBack data lives only on your device. To delete it, uninstall the app or clear the app's storage in Android Settings.

To request deletion of data you voluntarily submitted through a bug report, feature request, or Pro code redemption, use the privacy contact form with the subject PullBack data deletion request. Include the feedback ticket number or Pro code, if available, so we can find the correct record. We will delete the submitted text and its attached app, Android, device, timer, service-state, and progress context within 30 days. We may retain only what is required for fraud prevention, security, or legal compliance, and will explain any such retention in our response.

Signing out or clearing local storage does not erase shared account records. Google Play purchase records are also subject to Google's own retention controls.

8. Your privacy rights

If you are in a jurisdiction that grants additional rights (such as the EU under GDPR, the UK under UK-GDPR, or California under CCPA/CPRA), those rights still apply. Use the privacy contact form for data requests and we will respond within 30 days.

9. The marketing site (pullback.works)

This website uses self-hosted Umami for page views and allowlisted interactions. It does not set cookies. Form content and email addresses are never sent to analytics. You can opt out at /?analytics=off and turn it back on at /?analytics=on.

Optional contact content is delivered to our private Telegram channel through an authenticated notification pipeline. A draft is kept in sessionStorage for the current browser tab so it survives a reload, then cleared when you confirm sending or explicitly discard it.

10. Changes to this policy

If PullBack changes its data practices, this policy will be updated and the relevant sections will describe the change. The effective date at the top will reflect the update. Material changes will also be surfaced inside the app when applicable.

The current version of this policy will always be available at https://pullback.works/privacy and inside the PullBack app under Settings → Privacy policy.

11. Contact

For privacy questions, data access requests, or anything else related to this policy:

• Open the privacy contact form

We aim to respond within 7 business days. Because PullBack is a small project, we ask for your patience if a response takes a little longer.

---

This policy is provided as a clear, plain-language summary of how PullBack handles data. It is not legal advice. If you require a formal legal review or have specific regulatory questions about your use of PullBack in your jurisdiction, please consult a qualified attorney.