Play Store privacy details

From April 2022, apps on the Google Play Store will need to submit privacy details about their app. On each app’s product page, users will be able to see the data the app may collect, and whether that data is linked to them or used to track them.

This page provides information on how the data captured by BugSnag and its usage relates to the guidance from Google.

Types of data

The automatically captured data page provides information on what data BugSnag captures by default, and guidance on preventing capture of each type of data. BugSnag can be configured to override any automatically captured data, and also send custom additional metadata. Custom metadata you choose to send is of course out of the scope of this document.

The following table describes how Google’s definition of data types relate to BugSnag’s automatically captured data, to aid providing privacy information for an app.

Data Automatically captured by BugSnag
Approximate location No.
Precise location No.
Personal info
Name No.
Email address No.
Personal identifiers No.
Address No.
Phone number No.
Race and ethnicity No.
Political or religious beliefs No.
Sexual orientation or gender identity No.
Other personal info No.
Financial Info
Credit card, debit card, or bank account number No.
Purchase history No.
Credit info No.
Other financial info No.
Health and fitness
Health information No.
Fitness information No.
Emails No.
SMS or MMS messages No.
Other in-app messages No.
Photos or videos
Photos No.
Videos No.
Audio files
Voice or sound recordings No.
Music files No.
Other audio files No.
Files and docs
Files and docs No.
Calendar events No.
Contacts No.
App activity
Page views and taps in app No.
In-app search history No.
Installed apps No.
Other user-generated content No.
Other actions Yes. Breadcrumbs are stored and sent with each event report. You can override which breadcrumbs are captured with Android enabledBreadcrumbTypes. Or, you can amend and delete individual breadcrumbs with an Android onBreadcrumb callback in Android, React Native, and Cocos2d-x projects.

If your application uses React Native or Expo, JavaScript breadcrumbs are additionally captured. You can prevent capture of these with React Native enabledBreadcrumbTypes or Expo enabledBreadcrumbTypes configuration.

User interaction and navigation type breadcrumbs are captured for React Native, Unity and Unreal Engine projects. These include details of which selectors are clicked, their text value and the user’s journey through the application, so consider for your app whether these breadcrumbs contain any other types of data. You can amend or remove these using the React Native addOnBreadcrumb, the Unity enabledBreadcrumbTypes or Unreal Engine addOnBreadcrumb configuration options.

Sessions are tracked by default with the BugSnag notifiers. You can disable automatic session tracking for each platform as follows: Android, React Native, Cocos2d-x, Expo, Unity, Unreal Engine
Web browsing
Web browsing history No.
App info and performance
Crash logs Yes. We also send “internal” crash reports when there is a crash in BugSnag library code. This can be disabled with the telemetry configuration option.
Diagnostics Yes.
Other app performance data Yes. BugSnag additionally captures application information by default.
Device or other identifiers
Device or other identifiers User ID. An overridable unique identifier is generated for the value if no user data is set.

Device ID. An overridable unique identifier is generated for the value. Note that the original device ID will still be used in crash reporting internal to the BugSnag SDK.

You can automatically redact keys in metadata by adjusting the redactedKeys configuration option.

Data purpose

SmartBear does not use event data from customer applications for any of the purposes outlined by Google. We process data on behalf of each BugSnag customer to provide data analytics about crashes and application stability to that customer (the data controller).

However, by using BugSnag, you may be using data in the ways described below.

Data purpose Applicable to your use of BugSnag?
App functionality No.
Analytics Yes. You can use BugSnag to minimize app crashes, and improve stability.
Developer communication No.
Advertising or marketing No.
Fraud prevention, security, and compliance No.
Personalization No.
Account management No.

Data linked to the user

If you are setting user data, then you need to be aware that all reports sent to BugSnag can be linked to that individual user. By default BugSnag captures a unique user ID (per device) so that reports from the same user can be linked, even if no user data is associated with the reports.

This unique ID can be removed by setting null for each of the fields in setUser. There is also a field which uses the same id as the default user id. This can be overriden if required. However note that the default device / user ID will still be used for internal crash reports, where the error came from the BugSnag SDK itself.

Encryption in transit

Communications between your application and BugSnag servers are encrypted via industry best-practice HTTPS and Transport Layer Security (TLS) by default.

Deleting Data

There is no mechanism to delete previously collected data via the BugSnag Android notifier directly. Developers that have access to their organisation’s BugSnag dashboard can delete any information that has been previously collected. It is also possible to delete information specific to individual users.


You will have the ability to add links on your product page to your app’s privacy policy and your privacy choices. Should you wish to reference our privacy policy this is on the SmartBear website.