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.
1. Plain-English summary
- Core app timing stays on your device. PullBack has no account, login, ads, advertising SDK, analytics SDK, or cloud sync. Foreground package names and session events used by the timer are stored only on your device.
- 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.
- AccessibilityService data is not transmitted, sold, or shared. It is used only for foreground-app timing, session recovery, stats, and PullBack's core interruption feature.
- 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.
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:
| Data | Why | Stored? |
|---|---|---|
| The package name of the app currently in the foreground | To start, pause, recover, and end the timer for apps you selected. Uses Android's AccessibilityService API. | Session events are stored in a local Room database for timer recovery and stats. They stay on your device. |
| Window-change events and limited interactive-window metadata | To detect foreground changes and avoid treating picture-in-picture windows as the foreground app. | Processed on device. PullBack does not read or store window text or screen content. |
| Your settings, selected apps, timers, schedules, and master toggle | To remember your preferences across launches. | Android DataStore on your device. Stays on device. |
| The list of launchable apps installed on your device | To show apps you can choose for PullBack. | Read on demand from Android's PackageManager. Your selected package names are stored locally. |
| Your save count, streak, and time-saved totals | To show your progress in the app. | Android DataStore and the local session database. Stays on device. |
PullBack does not access:
- The content of any app you open (no screenshots, no screen recording, no text scraping).
- Your messages, calls, contacts, photos, 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.
- Device identifiers, advertising IDs, or any persistent identifier sent off-device.
3. Data sent off-device
PullBack does not include analytics, advertising, or automatic crash-reporting SDKs. AccessibilityService data is not sent off-device.
- Google Play purchases. Subscription and lifetime purchase activity is handled by Google Play under Google's privacy terms. PullBack stores only the resulting entitlement state on your device.
- 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 transiently by Google Play or the hosting provider when completing a network request.
- We do not include advertising SDKs.
- We do not share data with any third party for advertising or marketing purposes.
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 only for Google Play billing, 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 this data. There is no backup target other than the system-default backup behavior provided by Android (which is encrypted and tied to your Google account, not to PullBack). You can disable Android backups for PullBack in your device's backup settings.
When you uninstall PullBack, all of its locally stored data is deleted by Android.
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. Delete your data
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.
PullBack has no user accounts. Google Play purchase records are managed by Google under Google's own account and 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 a future version of PullBack changes its data practices, for example by introducing a new SDK or backend service, this policy will be updated, and the relevant section of the policy will name the SDK, what it accesses, and how it is governed. The "Last updated" date at the top of this policy will reflect the change. Material changes will also be surfaced inside the app on next launch.
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:
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.