Google Play Data safety (Android)

Google Play require developers to declare how they collect and handle user data within their app. The provided information is shown on the Google Play store listing.

This table provides guidance for publishing apps incorporating our Snowplow Android Tracker.

Category	Data type	Description	Snowplow Android TrackerFeature
Location	Approximate location	User or device physical location to an area greater than or equal to 3 square kilometers, such as the city a user is in, or location provided by Android’s ACCESS_COARSE_LOCATION permission.	✅ Geolocation context (optional and disabled by default in TrackerConfiguration geoLocationContext)
	Precise location	User or device physical location within an area less than 3 square kilometers, such as location provided by Android’s ACCESS_FINE_LOCATION permission.
App activity	Page views and taps in app	Information about how a user interacts with your app. For example, the number of page views or the screen coordinates of taps.	✅ ScreenView automatic tracking (optional but enabled by default in TrackerConfiguration screenViewAutotracking)
	In-app search history	Information about what a user has searched for in your app.	❌
	Installed apps	Information about the apps installed on a user's device.	❌
	Other user-generated content	Any other user-generated content not listed here, or in any other section. For example, user bios or notes.	❌
	Other actions	Any other user activity or actions in-app not listed here such as gameplay and likes.	✅ Session automatic tracking (optional but enabled by default in TrackerConfiguration sessionContext) ✅ Background–Foreground transition tracking (optional and disabled by default in TrackerConfiguration lifecycleAutotracking)
Web browsing	Web browsing history	Information about the websites a user has visited.	❌
App info and performance	Crash logs	Crash log data from your app. For example, the number of times your app has crashed, stack traces, or other information directly related to a crash.	✅ Crash reporting automatic tracking (optional but enabled by default in TrackerConfiguration exceptionAutotracking)
	Diagnostics	Information about the performance of your app. For example battery life, loading time, latency, framerate, or any technical diagnostics.	✅ Platform context (optional but enabled by default in TrackerConfiguration platformContext)
	Other app performance data	Any other app performance data not listed here.	❌
Device or other identifiers	Device or other identifiers	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.	✅ Advertising identifier (AAID, also called IDFA) (optional, enabled by default as part of TrackerConfiguration platformContext but also requires extra configuration)

note

The IP address of the device can be tracked by the collector. Disable this using server-side anonymisation.