Google Play Data Safety

A reference for providing information for Google Play’s Data safety section

Use this table to help fill out the Google Play data safety section in Play console. The Airship SDK can be configured to not require any data (all features disabled), but some data maybe be required based on the app’s usage of the SDK.

Data Category	Details
Location	If location module is used, lat/longs will be requested on behalf of the application but Airship does not upload or store the location lat/longs.
Personal Info	Only collected if the app uses the Airship SDK to gather such data. (e.g., first name with attributes)
Financial Info	Only collected if the app uses the Airship SDK to gather such data. (e.g., purchase history with custom events)
Health and Fitness	Only collected if the app uses the Airship SDK to gather such data. (e.g., favorite type of workout with attributes)
Messages	User messages are collected only if Chat module is enabled.
Photos or videos	Airship does not collect photos or video files from users.
Audio files	Airship does not collect audio or music files from users.
Files and docs	Airship does not collect files or docs from users.
Calendar	Airship does not collect calendar events or information from users.
Contacts	Airship does not collect contacts from users.
App activity	Some app activity data is collected if analytics is enabled, including analytic lifecycle events (e.g., app foreground and background), message center message status, notification opt-in status, in-app automation events, and push responses (e.g., buttons, quick reply). Other app activity data may be collected, such as custom events and screen views, if the app uses the Airship SDK to gather such data.
Web browsing	Airship does not collect browsing history from users
App info and performance	Airship does not collect crash logs or diagnostics.
Device or other IDs	Airship creates a device-level ID called a channel ID for functionality and analytics purposes. It is not linked to a user’s identity. If using push notifications, push token is collected. If using Contacts, Airship creates a Contact ID that is linked to the channel ID. It can be tied to the user’s identity if configured by the app. Otherwise, it is anonymous. If using Message Center, Airship generates Message Center user credentials. Other identifiers may be collected, such as Advertising ID, if the app uses the Airship SDK to gather such data.

Feedback

Was this page helpful?