Formulario de seguridad de datos de Google Play
The following section provides information to help you understand the impact of D1 SDK to your issuer application by submitting the Google Play data safety form.
This page only covers the scope of D1 SDK.
You may receive different answers from your submission of the Google Play data safety form due to additional processing, transfer, or storage done by your issuer application.
Data safety questions
These are the fields that are required in the Google Play data safety form:
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 D1 backend.
Is all of the user data collected by your app encrypted in transit?
Yes
Traffic to D1 backend is encrypted in transit.
Do you provide a way for users to request that their data is deleted?
No
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 more information about the data types used, refer to the Google documentation.
Personal Info
Name
How a user refers to themselves. For example, their first name, last name, or nickname.
No
N/A
N/A
N/A
N/A
N/A
Personal Info
Email address
Yes (for MC Click2Pay)
Yes
Yes
Fraud prevention, security, and compliance
Yes
Fraud prevention, security, and compliance
Personal Info
User IDs
Identifiers that relate to an identifiable person. For example, an account ID, account number, or account name.
Yes (consumerId as part of SDK APIs)
No (stored on D1 backend)
No
App functionality
No
N/A
Personal Info
Address
For example, a user's mailing or home address
No
N/A
N/A
N/A
N/A
N/A
Personal Info
Phone Number
No
N/A
N/A
N/A
N/A
N/A
Personal Info
Race and ethnicity
No
N/A
N/A
N/A
N/A
N/A
Personal Info
Political or religious beliefs
No
N/A
N/A
N/A
N/A
N/A
Personal Info
Sexual orientation
No
N/A
N/A
N/A
N/A
N/A
Personal Info
Other info
Any other personal information. For example, a user's date of birth, gender identity, or veteran status.
No
N/A
N/A
N/A
N/A
N/A
Financial Info
User Payment Info
Information about a user's financial accounts. For example, their credit card number.
No
N/A
N/A
N/A
N/A
N/A
Financial Info
Purchase History
Information about purchases or transactions a user has made
Yes
Yes
No
App functionality
No
N/A
Financial Info
Credit Score
No
N/A
N/A
N/A
N/A
N/A
Financial Info
Other financial Info
Any other financial information. For example, a user's salary or debts.
No
N/A
N/A
N/A
N/A
N/A
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 (AndroidId is used for D1Pay and passed to D1 backend)
No
No
App functionality
No
N/A
Última actualización
¿Te fue útil?