Google Play's data safety form

This section helps you understand how the Push Provisioning SDK affects your mobile application when you complete the Google Play Data safety form.

Note

• This page only covers the scope of the Push Provisioning SDK.
• You may see different responses in the Google Play Data safety form if your application performs additional processing, transfer, or storage.

Data safety questions

These fields are required in the Google Play Data safety form:

Question	Answer	Comments
Does your app collect or share any of the required user data types?	Yes	Our service relies on several data types to be captured and sent to server.
Is all of the user data collected by your app encrypted in transit?	Yes	Traffic to server is encrypted in transit.
Do you provide a way for users to request that their data is deleted?	No	Users have access to the APIs to remove the user data types stored.
Is your app currently certified by an authorized lab, according to the Mobile Application Security Assessment (MASA) framework?	No	This certification is managed at the application level.

Data types used

For details on these data types, see the Google documentation.

Category	Data type	Description	Is Data Collected?	Is Data processed ephemerally?	Is Data Optional?	Purpose of data collection	Is Data shared?	Purpose of data sharing
Device or other IDs	Device or other IDs	Identifiers that relate to an individual device, browser, or app. For example, an IMEI number, MAC address, Widevine Device ID, Firebase installation ID, or advertising identifier.	Yes (WalletId from OEM)	Yes	No	App fun