Data Safety Form Helper
Generate exact, compliant answers for Google Play’s Data Safety questionnaire. Automatically maps SDKs (AdMob, Firebase, Crashlytics, Auth, Billing) to required data disclosures, collection vs sharing, ephemeral flags, and deletion declarations.
100% client-side · Private by design · No account required
1. App Details & Governance
Core security disclosures required on Page 1 of Google Play Data Safety.
2. Select Third-Party SDKs & Libraries
Click the SDKs included in your build. The required Google Play Data Safety disclosures are auto-calculated.
3. Additional First-Party Data Collection
Select any additional data your own backend or app code collects from users.
0 custom data types added
4. Play Console Questionnaire Answers
Copy or download these exact answers to fill out Google Play Console > App content > Data safety.
1
Play Console Page 1: Data Collection & Security
- Does your app collect or share any user data? YES
- Is all data encrypted in transit? YES
- Do you provide a way for users to request deletion? YES
2
Play Console Page 2: Data Types to Check (6 selected across 4 categories)
App activity
✓ App interactionsFirebase Analytics
✓ In-app search historyFirebase Analytics
App info & performance
✓ Crash logsFirebase Crashlytics
✓ DiagnosticsFirebase Crashlytics
Device or other IDs
✓ Device or other identifiersFirebase Analytics, Firebase Crashlytics
Location
✓ Approximate locationFirebase Analytics
3
Play Console Page 3: Per-Data-Type Declarations
App activity
App interactions
Collected: YesShared: No
Ephemeral processing:No (Stored/transferred)
Required vs Optional:Required
Declared Purposes:
Analytics
App activity
In-app search history
Collected: YesShared: No
Ephemeral processing:No (Stored/transferred)
Required vs Optional:Required
Declared Purposes:
Analytics
App info & performance
Crash logs
Collected: YesShared: No
Ephemeral processing:No (Stored/transferred)
Required vs Optional:Required
Declared Purposes:
App functionalityAnalytics
App info & performance
Diagnostics
Collected: YesShared: No
Ephemeral processing:No (Stored/transferred)
Required vs Optional:Required
Declared Purposes:
App functionalityAnalytics
Device or other IDs
Device or other identifiers
Collected: YesShared: No
Ephemeral processing:No (Stored/transferred)
Required vs Optional:Required
Declared Purposes:
AnalyticsApp functionality
Location
Approximate location
Collected: YesShared: No
Ephemeral processing:No (Stored/transferred)
Required vs Optional:Required
Declared Purposes:
Analytics
=================================================================
GOOGLE PLAY DATA SAFETY DECLARATION GUIDE FOR: MY ANDROID APP
Generated on: 23/09/2026
=================================================================
--- SECTION 1: DATA COLLECTION AND SECURITY (Page 1 in Play Console) ---
1. Does your app collect or share any of the required user data types?
-> Answer: YES
2. Is all of the user data collected by your app encrypted in transit?
-> Answer: YES (All transmissions use TLS/HTTPS)
3. Do you provide a way for users to request that their data is deleted?
-> Answer: YES
--- SECTION 2: DATA TYPES TO SELECT (Page 2 in Play Console) ---
Tick the checkboxes for the following categories and data types:
[Category: App activity]
[X] App interactions (Page views, button taps, screen time, navigation flow)
Active via: Firebase Analytics
[X] In-app search history (Search queries entered by the user inside the app)
Active via: Firebase Analytics
[Category: App info & performance]
[X] Crash logs (Stack traces, crash dumps, and exception reports)
Active via: Firebase Crashlytics
[X] Diagnostics (App launch time, frame rate, battery and memory usage)
Active via: Firebase Crashlytics
[Category: Device or other IDs]
[X] Device or other identifiers (Advertising ID (GAID), Android ID, IMEI, MAC address, FCM token)
Active via: Firebase Analytics, Firebase Crashlytics
[Category: Location]
[X] Approximate location (Location within an area of 3+ square km (network location, IP derived))
Active via: Firebase Analytics
--- SECTION 3: DATA USAGE AND HANDLING (Page 3 in Play Console) ---
For each selected data type, answer the questions as follows:
1. Data Type: App interactions (Category: App activity)
• Is this data collected? -> YES
• Is this data shared with third parties? -> NO
• Is this data processed ephemerally? -> NO
• Is this data collection required or optional? -> REQUIRED (Users cannot turn it off)
• Purposes to check:
[X] Analytics
2. Data Type: In-app search history (Category: App activity)
• Is this data collected? -> YES
• Is this data shared with third parties? -> NO
• Is this data processed ephemerally? -> NO
• Is this data collection required or optional? -> REQUIRED (Users cannot turn it off)
• Purposes to check:
[X] Analytics
3. Data Type: Crash logs (Category: App info & performance)
• Is this data collected? -> YES
• Is this data shared with third parties? -> NO
• Is this data processed ephemerally? -> NO
• Is this data collection required or optional? -> REQUIRED (Users cannot turn it off)
• Purposes to check:
[X] App functionality
[X] Analytics
4. Data Type: Diagnostics (Category: App info & performance)
• Is this data collected? -> YES
• Is this data shared with third parties? -> NO
• Is this data processed ephemerally? -> NO
• Is this data collection required or optional? -> REQUIRED (Users cannot turn it off)
• Purposes to check:
[X] App functionality
[X] Analytics
5. Data Type: Device or other identifiers (Category: Device or other IDs)
• Is this data collected? -> YES
• Is this data shared with third parties? -> NO
• Is this data processed ephemerally? -> NO
• Is this data collection required or optional? -> REQUIRED (Users cannot turn it off)
• Purposes to check:
[X] Analytics
[X] App functionality
6. Data Type: Approximate location (Category: Location)
• Is this data collected? -> YES
• Is this data shared with third parties? -> NO
• Is this data processed ephemerally? -> NO
• Is this data collection required or optional? -> REQUIRED (Users cannot turn it off)
• Purposes to check:
[X] Analytics
Why Google Play Data Safety Matters
Google Play’s Data Safety section is mandatory for every app published on Google Play. It provides store visitors with transparent disclosure regarding what personal data and device identifiers are collected, whether that data is shared with third parties, how it is encrypted, and how users can request deletion.
The Common Rejection Pitfall: Third-Party SDKs
The majority of Data Safety rejections happen not because of custom developer code, but because of third-party SDKs. Google Play runs static bytecode analysis and dynamic sandbox tests on your submitted APK or AAB. If your build contains libraries like Google Mobile Ads (AdMob), Firebase Analytics, Facebook SDK, or OneSignal, Google’s automated verification checks for the corresponding declarations:
- AdMob: Requires declaring Advertising ID and Approximate Location as both Collected and Shared for advertising, analytics, and fraud prevention.
- Firebase Analytics & Crashlytics: Requires declaring Crash logs, Diagnostics, Device identifiers, and derived Approximate location.
- Account Authentication: Requires declaring Name, Email, and User IDs, along with a valid public Account Deletion URL.
How to Use This Helper
- Select the SDKs included in your Gradle dependencies.
- Tick any extra first-party data types your app collects directly.
- Check the live Play Console questionnaire cheat sheet below.
- Follow Section 1, Section 2, and Section 3 inside Play Console (App Content > Data safety).
Frequently asked questions
- Why does Google Play reject apps on Data Safety?
- The number one reason for Data Safety rejections is undeclared third-party SDK collections. When you include AdMob or Firebase in your build, Google’s automated review scanners detect their classes and permissions. If your Data Safety declaration says you collect no data, or omits "Advertising ID" / "Approximate location", Play Console flags an immediate policy violation.
- What is the difference between Data Collected vs Data Shared?
- Data is "Collected" when data leaves the user’s device and is transmitted to your own servers or processed by service providers on your behalf. Data is "Shared" when data is transferred to a third party that uses it for their own purposes (such as ad networks like AdMob or Meta using the Advertising ID to target ads across multiple apps).
- What does "Ephemeral Processing" mean in Google Play?
- Data is processed ephemerally ONLY if it is accessed in memory and immediately discarded without being written to disk, sent to a server, or kept after handling the immediate request (e.g., weather lookup based on coordinates where the location is never logged). If data is sent to Firebase or AdMob, it is NOT ephemeral.
- What is the mandatory Account Deletion URL requirement?
- Since late 2023, Google Play requires all apps that allow account creation to provide a web-based Account Deletion URL where users can request account and data deletion without needing to reinstall the app or use an in-app button. You must provide a valid public webpage URL.
- Do I have to declare data collected by Firebase Analytics or Crashlytics?
- Yes. Even though Firebase is a developer tool, Google Play requires developers to disclose every data type collected by Firebase, including Crash logs, Diagnostics, Device IDs, and Approximate location (derived from IP).
- Does this tool send my app data to a server?
- No. Everything is computed entirely in your browser with client-side TypeScript. No information is stored, logged, or sent over the network.