Articles in this section

See more

Google Play's Data Safety Form

Manuel Gonzales
  • Updated
Follow

Overview

A user is looking for assistance filling in the new Data Safety form from Google which was recently introduced. Furthermore, users have been receiving emails prompting them to complete the form.

Hello Google Play Developer,

Earlier this year, we announced new policy requirements for the upcoming Data safety section in Google Play. With this feature, you'll have a clear way to show your users how you keep their data safe and explain what data your app collects and why.

Your Data safety form is ready for you to fill out. Go to App Content in your Google Play Console to get started.

We want to make sure you have ample time and resources to get prepared ...

 

Solution

The idea behind this change is that with the new Data safety section, you will now have a transparent way to show users if and how they collect, share, and protect user data before users install an app.

The form involves 5 different steps and depending on the BiznessApps features you are using, you would need to select different options.

For further information on the details of each data type and what it entitles, refer to Provide information for Google Play's Data safety section. Additionally, there is also an official Android Walkthrough Video of these steps.


Step 1 - Overview

This section just provides a short explanation of what the form entitles, and you can press Next after reading it.

 

mceclip0.png

 

Step 2 - Data Collection and Security

This section contains 3 different questions and the answer would be Yes to all of them if you are using at least one of the features listed in Step 3 - Data Types.

On the other hand, if you are not using any of those features, then you can select No to the first question and go directly to Step 5 - Preview.

 

mceclip1.png

 

Note: You would need to Contact Support to request the deletion of user data on the backend. 

 

Step 3 - Data Types

This step has different sections based on the type of data, and the table below shows the options you would need to select/check depending on the feature(s)* the app is using.

mceclip2.png

Feature 

Location

Personal Info

Financial Info

Photos or Videos

Audio Files

App Activity
Car Finder
  • Approximate location
  • Precise Location
    
  • Photos
    
Custom Forms  

Depending on the fields used, these are the common ones

  • Name
  • Email address
  • Address
  • Phone number
  • Other personal info
        
Email Photo  
  • Email address
  
  • Photos
    
Events v2  
  • Name
  • Email address
      
  • Other user-generated content (Comments)
Fan Wall v2  
  • Name
  • Email address
  
  • Photos
  
  • Other user-generated content (Comments)
Food Ordering  
  • Name
  • Email address
  • Address
  • Phone number
  • Credit Card (if available as payment method)
  • Purchase history
      
Golf Course  
  • Name
  • Email address
        
Geofenced Push Notifications
  • Approximate location
  • Precise Location
          
Loyalty

It only applies if GPS validation is enabled.

  • Approximate location
  • Precise Location
          
Mailing List  
  • Name
  • Email address
  • Address
  • Other personal info (Birthday)
        
Groups (Membership)  
  • Name
  • Email address
        
Merchandise  
  • Name
  • Email address
  • Address
  • Phone number
  • Credit Card (if available as payment method)
  • Purchase history
      
Notepad          
  • Other user-generated content (Notes)
Reservation  
  • Name
  • Email address
  • Phone number
  • Credit Card (if available as payment method)
  • Purchase history
      
Sign Up  
  • Name
  • Email address
  • Other personal info (Birthday)
        
Sports Stats  
  • Email address
      
  • Other user-generated content (Stats)
Voice Recording  
  • Email address
    
  • Voice or sound recordings
  
WebSite  

It would depend on the site embedded in your app.

  • Name
  • Email address
      

It would depend on the site embedded in your app.

  • Other user-generated content
WuFoo Form  

It would depend on the form used, these are the common ones

  • Name
  • Email address
  • Address
  • Phone number
  • Other personal info
        

* Only features that use a data type are listed. Also, only the data type categories used by BiznessApps are part of the table.

 Once you have selected all of the data types that apply to your app, press Next.

 

Step 4 - Data Usage and Handling

In this step, we need to define the usage and handling for each of the data types previously selected in Step 3.

mceclip4.png

Note: Something important to consider with the column on the data being required is whether the feature collecting that data type is one of the main features of the app or something optional. For instance, the Fan Wall is not something users must fill in so the data type there would be optional (if not used in other features). On the other hand, if the main use of your app is for Food Orders, then the relevant data types (name, email, etc) would be required as otherwise, the app would have no use to clients.

 

Data Type

Is the data collected, shared?

Is this data processed ephemerally?

Is this data required for your app?*

Why is this user data collected?
Approximate Location Collected Yes Required
  • App Functionality
Precise Location

Collected

Yes, if used for Loyalty GPS validation.

No, if used for Push Notifications or Car Finder.

 Required
  • App Functionality
Name Collected No Required
  • App Functionality
  • Analytics
  • Account Management
Email address Collected No Required
  • App Functionality
  • Analytics
  • Advertising or marketing (Mailing List)
  • Account Management
Address Collected No Required
  • App Functionality
  • Account Management
Phone Number Collected No Required
  • App Functionality
  • Account Management
Other Personal Info Collected No Optional
  • App Functionality
Credit Card (User Payment Info.) Collected Yes Optional
  • App Functionality
Purchase History Collected No Required
  • App Functionality
  • Analytics
Photos Collected No Optional
  • App Functionality
Voice or sound recordings Collected No Optional
  • App Functionality
Other user-generated content Collected No Optional
  • App Functionality
Device and other IDs (some common examples may include Advertising ID, Android ID, IMEI, BSSID)
 Collected No Required
  • App Analytics

* This is the usual scenario, but read the note above to understand which applies to your app.

Once you have completed the information for every data type, press Next.

 

Step 5 - Preview

Here you will be prompted with the summary of the options you selected, and how the data collection is handled. Review the information to ensure it matches your app behavior, and then press Submit.

 

mceclip3.png

Once submitted, the Google Play team will review the information and provide feedback if applicable.

Related articles

Comments

0 comments

Please sign in to leave a comment.