Completing the Google Data Safety form for your Pugpig app
Data safety is a new section you'll start seeing in the Google Play console when managing and submitting updates to your app. This comes with a couple of new requirements, which if not followed will prevent you from submitting these updates.
Secondly, the new Data Safety form needs to be filled out for all apps. This document serves to guide you through the process of filling out the form, which is a requirement for all apps listed on the Google Play Store. This form should only have to be filled out once per app.
The headings and questions below should match those in the form (though the form is, of course, subject to change). Note that many of these questions depend on the exact configuration of your app and the choice of services you integrate with.
These recommendations are our guidance for filling out the form, and you can safely follow it word-for-word. However, if you’ve received alternative guidance or believe one of our suggestions to be incorrect, feel free to diverge from this guidance. When in doubt we’ve erred on the side of saying there is more data collection, rather than less.
Data collection and security
1. Does your app collect or share any of the required user data types?
2. Is all of the user data collected by your app encrypted in transit?
3. Which of the following methods of account creation does your app support?
Answer: This is specific to your app. If your app does not allow users to create an account, choose no, note that questions 3a and 3b will not appear. If it does, select the choice that applies.
3a. Add a link that users can use to request that their account and associated data be deleted
Answer: This will be the URL you've provided us to included in your app settings page that takes users to a screen where they can request said deletion
3b. Do you provide a way for users tor request that some or all of their data be deleted without requiring account deletion.
Answer: Again, this is specific to your auth system and implementation. Choose the answer that applies.
4. Do you provide a way for users to request that their data is deleted?
Yes: Approximate location
No: Precise location
2. Personal info
This is entirely dependent on your configuration and should be answered by the data you have access to (i.e in your analytics or other data platform. Pugpig doesn’t collect any additional data.
3. Financial info
Yes: Purchase history
No: User payment details, credit score, other financial information
4. Health and fitness
6. Photos and videos
7. Audio files
8. Files and docs
11. App activity
Yes: App interactions, in-app search history
No: Installed apps, other user-generated content, other actions
12. Web browsing
13. App info and performance
Yes: Crash logs, Diagnostics, other app performance data
14. Device or other IDs
Yes: Device or other IDs
Data usage and handling
1. Is the data, collected, shared, or both?
For all types, select only collected
2. Is the data processed ephemerally?
For all types, select No, this collected data is not processed ephemerally.
3. Is this data required for your app, or can users choose whether it's collected?
For all types, selected Data collection is required (users can’t turn off this data collection).
Exception: If you’re using our analytics opt-in functionality, you can choose “Users can choose whether this data is collected” for the following data types: App interactions, in-app search history.
4. Why is this user data collected? Select all that apply
Follow the table below to know which of the subsequent boxes to tick:
|App Functionality||Analytics||Developer comms||Advertising or marketing||Fraud prevention, security and compliance||Personalisation||Account management|
|In-app search history||No||Yes||No||No||No||No||No|
|Other app performance data||No||Yes||Yes||No||No||No||No|
|Device and other IDs||Yes||Yes||No||Yes||No||Yes||Yes|
That should be the end of the form. If anything isn’t clear, get in touch with firstname.lastname@example.org and we’ll help you out.