In May 2021, Google Play announced the new Data safety section , which is a developer-provided disclosure for an app's data collection, sharing, and security practices.
This page can help you complete the requirements for this data disclosure in regards to your usage of Google Pay Android SDKs. On this page, you can find information on whether and how our SDKs handle end-user data.
We aim to be as transparent as possible in supporting you; however, as the app developer, you are solely responsible for deciding how to respond to Google Play's Data safety section form regarding your app's end user data collection, sharing, and security practices.
How to use information on this page
This page lists the end-user data collected by only the latest version of each Google Pay Android SDK.
Each SDK has its own section later on this page where we provide information about data collected automatically versus data collected optionally . Automatic collection means that the SDK collects specific data without you invoking any specific method or class in your app. Optional collection means that the SDK collects specific data based on invocation and configuration in your app.
TapandPay SDK
For the collected end-user data types listed on this page, the TapandPay SDK encrypts the data in transit using HTTPS. End-users can request to delete collected data from the Google Pay app or via myaccount.google.com/deleteservices .
Data collected automatically
| Data | Data Type | By default, the TapandPay SDK... |
|---|---|---|
|
App Activity
|
Page Clicks | Collects this data type to maintain and improve TapandPay services. |
|
App Activity
|
Page Views | Collects this data type to maintain and improve TapandPay services. |
|
Approximate Location
|
Country of end-user | Collects this data type to facilitate our contactless payment service, and to determine service usage so that we can provide, maintain, and improve TapandPay services. |
|
Device or other identifiers
|
Device Identifier | Collects this data type to facilitate contactless payment services, and use them for fraud detection and prevention. |
|
Personal Information
|
Billing Address | Collects this data type to facilitate our contactless payment service. |
|
Personal Information
|
Collects this data type to facilitate contactless payment service and to use as a contact point for important service announcement notifications. | |
|
Personal Information
|
Name | Collects this data type to facilitate our contactless payment service. |
|
Personal Information
|
Phone Number | Collects this data type to facilitate our contactless payment service. |
Data collected optionally
| Data | Data Type | Depending on your app's configuration and invocation, the TapandPay SDK... |
|---|---|---|
|
Crash Logs
|
Application State | Collects anonymous stack traces, relevant SDK application state, and device metadata to monitor and improve the stability of the TapandPay services. This data type will not be linked to individual users. Users can opt out of collection by turning off "Usage & Diagnostics" . |
|
Crash Logs
|
Error Log Messages | Collects anonymous stack traces, relevant SDK application state, and device metadata to monitor and improve the stability of the TapandPay services. This data type will not be linked to individual users. Users can opt out of collection by turning off "Usage & Diagnostics" . |
|
Crash Logs
|
Stack Trace | Collects anonymous stack traces, relevant SDK application state, and device metadata to monitor and improve the stability of the TapandPay services. This data type will not be linked to individual users. Users can opt out of collection by turning off "Usage & Diagnostics" . |
Wallet SDK
For the collected end-user data types listed on this page, the Wallet SDK encrypts the data in transit using HTTPS. End-users can request to delete collected data from the Google Pay app or via myaccount.google.com/deleteservices .
Data collected automatically
Collects this data type to maintain and improve app analytics and app functionality. For example, this data type is collected to:
- Verify if registered merchants are invoking 3P SDKs.
Collects this data type for risk mitigation and fraud mitigation. For example, this data type is collected to:
- Pass to card network during device tokenization/device binding for cloud tokens.
- Associate a payment credential with a device.
Collects this data type to maintain and improve app analytics. For example, this data type is collected to:
- Measure and monitor anonymized conversion of buyflows.
Collects this data type to maintain and improve app analytics and app functionality. For example, this data type is collected to:
- Surface payment methods saved to Google Pay and are ready to be used for 3P purchase.
Data collected optionally
Collects this data type for the purpose of app functionality. For example, this data may be collected to:
- Save it as a future or current payment method.
- Return to the merchant in an encrypted payment token. The payment token can be decrypted by registered gateways for payment authorization.
Collects this data type for the purpose of app functionality. For example, this data type may be collected to be used:
- As one's legal address when creating payments customer profiles.
- As a billing address when saving a billing address.
- As a shipping address when saving shipping addresses.
- To return an item to the merchant in billing/shipping addresses, if requested.
Collects this data type for the purpose of app functionality. For example, this data type may be collected to:
- Create payments customer profiles.
- Be used as the card holder's name when saving cards.
- Return an item to the merchant in billing/shipping addresses, if requested.
Collects this data type for the purpose of app functionality. For example, this data type may be collected to:
- Save a billing/shipping address.
- Return an item to the merchant in billing/shipping addresses, if requested.
Play-Services-Pay SDK
For the collected end-user data types listed on this page, the Play-Services-Pay SDK encrypts the data in transit using HTTPS. End-users can request to delete collected data from the Google Pay app or via myaccount.google.com/deleteservices .
Data collected automatically
| Data | Data Type | By default, the Play-Services-Pay SDK... |
|---|---|---|
|
App Activity
|
Page Clicks | Collects this data type to maintain and improve the service. |
|
App Activity
|
Page Views | Collects this data type to maintain and improve the service. |
|
Crash Logs
|
Application State | Collects anonymous stack traces, relevant SDK application state, and device metadata to monitor and improve the stability of the service. |
|
Crash Logs
|
Error Log Messages | Collects anonymous stack traces, relevant SDK application state, and device metadata to monitor and improve the stability of the service. |
|
Crash Logs
|
Stack Trace | Collects anonymous stack traces, relevant SDK application state, and device metadata to monitor and improve the stability of the service. |
|
Device Identifiers
|
Android ID | Collects this data type to manage valuables that are pinned to a specific device or for a specific account. This information is also used to monitor, maintain, and improve the service. |
|
Personal Information
|
Account ID | Collects this data type in order to manage valuables that are pinned to a specific account. The information is also used to monitor, maintain, and improve the service. |
|
Personal Information
|
Collects this data type to store valuables (passes) to Google Pay under the user's Google Account. |
