Summary
This page explains the intended declaration based on the current app code and documented RevenueCat setup. The submission in Play Console must always match the final AAB, SDK behavior, RevenueCat dashboard, customer attributes, and integrations at the moment of release.
Disclosure matrix
| Data category | Play status | Purpose / handling |
|---|---|---|
| Purchase history Product, subscription status, transaction identifiers, purchase tokens | Collected Not shared* | Purchase processing, restore, entitlement verification, subscription/refund status, and purchase analytics through Google Play and RevenueCat. |
| Installed apps Apps available for user selection | Local only | Displayed on the device so the user can choose apps. The selected list is not uploaded. |
| App activity Foreground detection and pause decisions | Local only | Triggers the pause screen and creates on-device history and reports. Not sent for analytics. |
| App settings Rules, custom text, delays, preferences | Local only | Personalizes app behavior on the device. |
| Device or other IDs | Conditional review | RevenueCat uses an anonymous App User ID for entitlement association. Final classification must match the SDK and dashboard configuration, including any customer attributes or attribution integrations. |
| Location, contacts, messages, photos, audio, health data | Not collected | Not needed for PauseFeed functionality. |
*Under Google Play's Data Safety definitions, transfers to a service provider processing data on the developer's behalf generally are not declared as “sharing.” This must be reassessed if RevenueCat data is forwarded to advertising, attribution, or other third parties.
Security practices
- Purchase communication uses encrypted network connections.
- Core app data is stored inside Android's app sandbox.
- Android backup is disabled for PauseFeed.
- Users can delete local data in the app and can use the developer contact on the Google Play listing to request deletion of the corresponding anonymous RevenueCat customer record.
- The app contains no advertising SDK and no third-party behavioral analytics SDK.
Google Play and RevenueCat may retain transaction records required for accounting, fraud prevention, purchase restoration, or law. Local deletion does not cancel a subscription or erase a Google Play transaction.
Permission context
Usage Access lets the app determine which app is in the foreground. PauseFeed uses this only to compare the foreground package against the list chosen by the user. Display over other apps allows the pause interface to appear. Neither permission is used to read the contents of another app.
A foreground service and persistent notification support reliable detection under Android rules. Boot completion may restore an already-enabled service after restart. These capabilities must also be accurately described in Play Console's permissions and foreground-service declarations.
Release-time Console checklist
- Scan the final release AAB and dependency tree, not only source files.
- Confirm RevenueCat has no advertising attribution integration or customer attributes that add personal data.
- Declare Financial info → Purchase history as collected, not processed ephemerally, required for paid entitlement management, and used for App functionality and Analytics.
- Review whether the anonymous RevenueCat identifier must be declared as User IDs or Device or other IDs under the current SDK guidance.
- Answer that data is encrypted in transit and provide the verified support channel through which a user can request deletion of the RevenueCat customer record.
- Keep the Play Console answers, this page, and the in-app Privacy Policy identical in substance.
For the binding legal explanation, read the Privacy Policy.