Google Play Console Helper

Google Play Data Safety Form Answers

Use this reference sheet to accurately complete Google Play Console's mandatory "Data safety" questionnaire when publishing PicPurge.

1. Data Collection & Security Overview

Does your app collect or share any user data?
Select: Yes
(Because Google Mobile Ads (AdMob) collects device IDs/advertising IDs, and optional Google Sign-In reads basic profile info.)
Is all of the user data collected by your app encrypted in transit?
Select: Yes
(All external communications made by Google AdMob and Google OAuth use HTTPS/TLS.)
Do you provide a way for users to request that their data be deleted?
Select: Yes
(Users can tap "Reset all cleaning progress" or log out of Google in Settings; uninstalling completely purges all local data.)

2. Specific Data Types to Declare

Photos and videos: Do you collect photos or videos?
Select: NO
Critical Note: PicPurge accesses photos strictly locally on-device. Google Play definition: "Data processed ephemerally on-device without being transmitted off the device is NOT considered collected." Therefore, photos are NOT collected.
Personal info: Name, Email address (if using Google Sign-In)
Select: Collected (Optional)
• Collected: Yes (when user signs in with Google)
• Shared: No
• Ephemeral processing: No (cached locally in Hive)
• Required or Optional: Optional (user can use app without signing in)
• Purpose: Account management
Device or other IDs (Advertising ID for Google AdMob)
Select: Collected and Shared
• Collected: Yes
• Shared: Yes (shared with Google AdMob)
• Ephemeral: No
• Required or Optional: Required
• Purpose: Advertising or marketing, Analytics

3. Declaration for All Files Access (MANAGE_EXTERNAL_STORAGE)

When submitting to Google Play, the Play Console will ask why PicPurge requires MANAGE_EXTERNAL_STORAGE. You can copy and paste the following declaration text:

"PicPurge is a dedicated gallery cleaner application whose core functionality is bulk media management, organization, and trashing across all device photo albums (Screenshots, WhatsApp, Camera, Downloads, DCIM).

To provide a fast, Tinder-style swipe cleaning experience with non-destructive instant Undo, the app must move user-decided media files atomically into a local trash holding directory (.pic_purge_trash) across external storage partitions without interrupting the user with system dialogs on every individual photo swipe.

Standard MediaStore Scoped Storage APIs interrupt the user with an OS confirmation modal for every single delete action, making rapid swipe-based photo purge functionally impossible without All Files Access."