If you're concerned about Bugfender's use of data on your application:
Bugfender does not track your users across apps or websites.
Bugfender does not use your user's data for their own purposes, nor sell it to third parties, for advertisement purposes, nor any other purposes.
Bugfender does not access the device’s advertising identifier (IDFA) nor the ID for Vendors (IDFV).
If you're developing an iOS application, you do not need to ask the user for permission with the AppTrackingTransparency framework, since Bugfender does not do "tracking" in the definition of Apple in connection with advertising.
If you gather personal data with Bugfender, you can sign a Data Processing Agreement with us, so that you and your users are protected under GDPR.
Nutrition Labels for the App Store:
Bugfender does not track users, and by default collects a minimal set of information about the device (see Which device data is automatically collected from users?).
Out of the categories Apple indicates, Bugfender collects:
Other Diagonstic Data, since you use Bugfender to collect application logs. This information is not linked to the user and not used for tracking.
Starting Fall 2023, the iOS SDK will include a .xcprivacy file with this statement.
Please note you may be collecting additional data with the help of Bugfender (your user's name, email, etc.), and you may be using it for additional reasons (analytics, product personalization, etc.). Also you may be linking this data to the user by adding custom key-values and using the data for tracking. If that's the case, you're responsible for declaring these uses of information in App Store Connect or your application's .xcprivacy file.
Look out for the following:
Product Interaction, if you enable automated UI logging or if you do manual logging to track interactions.
Crash Data, if you enable crash reporting.
Performance data, if you log anything related with performance.
Identifiers, if you use custom device key-values to associate the logs of a device with its owner or the device itself.
How should you respond to Google Play Console Data Safety form?
Does your app collect or share any of the required user data types? Yes, you are at least collecting "Device or other identifiers" (Bugfender generates an installation ID) and most likely you're also collecting "Page views and taps in app", "Crash logs", "Other actions", and "Other app performance data", depending on your specific configuration. Depending on what you're manually logging, you might be collecting data of other categories as well, for example the user's name or e-mail address.
Is all of the user data collected by your app encrypted in transit? Bugfender encrypts all data in transit.
Do you provide a way for users to request that their data is deleted? Bugfender provides a way to request user data deletion.
For each data type, you will be asked if the data is "Collected" or "Shared". Bugfender does not use nor share your data with any 3rd party, so you can safely mark "Collected" if you're not sharing it.
Is this data processed ephemerally? No, since Bugfender stores your logs for at least one day and up to 30 days, depending on your plan.
Is this data required for your app, or can users choose whether it's collected? That depends on your policy for activating Bugfender and for logging to it. If you require user consent before installing Bugfender.
Why is this user data collected? Probably you'll want to check at least "Analytics". If you use the User Feedback function of Bugfender, you'll also want to check "App functionality". If you use Bugfender for other purposes, you might want to check more boxes.