From December 8th 2020, apps on the App 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. Apps should be submitted to the App Store in line with Apple’s privacy guidelines.
This page provides information on how the data captured by Bugsnag and its usage relates to the guidance from Apple.
The use of Bugsnag does not meet the criteria for optional disclosure. The data collected by Bugsnag is not wholly provided by the user in the app interface, and the frequency of reporting cannot be guaranteed to be below a set threshold.
Therefore, you will need to consider the types of data that you are sending to Bugsnag from your application when completing your app’s privacy details.
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. You should consider additional data you’ve configured Bugsnag to send for your App Store privacy details.
The following table describes how Apple’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 |
|---|---|
| Contact Info | |
| Name | No. |
| Email address | No. |
| Phone number | No. |
| Physical address | No. |
| Other user contact info | No. |
| Health and Fitness | |
| Health | No. |
| Fitness | No. |
| Financial Info | |
| Payment info | No. |
| Credit info | No. |
| Other financial info | No. |
| Location | |
| Precise location | No. |
| Coarse location | No. |
| Sensitive Info | |
| Sensitive info | No. |
| Contacts | |
| Contacts | No. |
| User Content | |
| Emails or text messages | No. |
| Photos or videos | No. |
| Audio data | No. |
| Gameplay content | No. |
| Customer support | No. |
| Other user content | No. |
| Browsing History | |
| Browsing history | No. |
| Search History | |
| Search history | No. |
| Identifiers | |
| User ID | Yes. An overridable unique identifier is generated for the user.id value if no user data is set. |
| Device ID | Yes. An overridable unique identifier is generated for the device.id value. |
| Purchases | |
| Purchase history | No. |
| Usage Data | |
| Product interaction | Yes. Breadcrumbs are stored and sent with each event report. You can override which breadcrumbs are captured with Cocoa enabledBreadcrumbTypes. Or, you can amend and delete individual breadcrumbs with a Cocoa onBreadcrumb callback. If your application uses React Native, JavaScript breadcrumbs are additionally captured. You can configure which ones are captured with JavaScript enabledBreadcrumbTypes. User interaction breadcrumbs include details of which selectors are clicked and their text value, so consider for your app whether these breadcrumbs contain any other types of data. You can amend or remove them in your native Cocoa layer, or with a JavaScript onBreadcrumb callback. Sessions are tracked by default with the Bugsnag Cocoa notifier. You can disable automatic session tracking with the autoTrackSesssions configuration option. |
| Advertising data | No. |
| Other usage data | No. |
| Diagnostics | |
| Crash data | Yes. |
| Performance data | Yes. |
| Other diagnostic data | No. |
| Other Data | |
| Other data types | Bugsnag additionally captures application information by default. |
You can automatically redact keys in metadata by adjusting the redactedKeys configuration option.
Bugsnag, Inc. does not use event data from customer applications for any of the purposes outlined by Apple. We processes data on behalf of each Bugsnag customer to provide data analytics about crashes and application stability to that customer (the data controller). Full details are provided in our privacy policy.
However, by using Bugsnag, you may be using data in the ways described below.
| Data use | Applicable to your use of Bugsnag? |
|---|---|
| Third-party advertising | No. |
| Developer’s advertising or marketing | No. |
| Analytics | You may consider that you use Bugsnag for analytics purposes, such as planning new features, and measuring audience sizes. |
| Product personalization | No. |
| App functionality | Yes. You can use Bugsnag to minimize app crashes, and improve stability. |
| Other purposes | No. |
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 (based on the 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 nil for each of the fields in setUser. Please note that there is also a device.id field which stores the same UUID that should also be removed to unlink a user from a report.
According to Apple’s definition of tracking, Bugsnag does not implement tracking as we do not link data collected from our notifiers with any third-party data.
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 Bugsnag’s privacy policy this is available here.
Guidance on how your app’s users should contact you to request that you retrieve, amend or delete their data held within the Bugsnag platform can be seen here.