You're free to redistribute the policy language below for use within your organization's own data-privacy and cookie policies for web applications.
We use Dynatrace to gain insights into the performance of our web application and to understand how our users navigate through it. Dynatrace captures data like W3C timings, button clicks, link clicks, JavaScript errors, browser types, and geographic regions. This data helps us to continuously improve the performance of our offering and to identify and fix functional problems. For this to work correctly and effectively, Dynatrace requires use of a set of cookies.
If you've enabled the cookie op-in setting and explicitly request user-consent for tracking (see Configure data privacy settings for web applications for details), then it's recommended that you use the following language in your organization's cookie policy:
Allow Dynatrace to capture performance data related to button clicks, page loads and web requests that are triggered along my journey through this web application. This enables Dynatrace to analyze application usage, improve performance, and address any troubles that may arise. Accepting this setting also enables Dynatrace cookies.
If you've enabled the RUM setting for considering do-not-track headers, it's recommended that you use the following language in your organization's privacy notice:
You can enable Enable your browser's built-in do-not-track feature to ensure that no personal data is captured.
We use Dynatrace to analyze usage patterns, optimize performance, and troubleshoot issues related to this app. Personal data may be captured during the course of monitoring. We won't share or sell any personal data. This data is utilized only for analyzing app usage and performance.
What data is collected? Dynatrace captures data related to button clicks and web requests that are sent by this app. Error messages and stack traces are captured when crashes occur. The only personal information Dynatrace collects is the email address you use to log into this app.
Note that email addresses aren't captured out of the box. If you don't use tags to tag your users for user session analysis, you can omit the last paragraph in the notice above. If you record other personal data, you should document your guidelines for protecting such data.
With mobile apps, you can enable user opt-in mode initially and then begin monitoring of those users who have explicitly given their consent to share their usage data. When user opt-in mode is active, OneAgent for Mobile starts with monitoring disabled. Monitoring must then be enabled manually via an API call for each user, following their consent to your privacy policy.
If your application uses opt-in mode, you may re-use the following text blocks to create a privacy settings page in your app that explains those privacy controls that relate to Dynatrace mobile application monitoring. Every text block describes a toggle button that allows every user to store his preferences. Whenever the user changes his preferences you can use mobile agent API calls to control the data collection level and whether crash reporting is enabled or disabled.
Allow Dynatrace to capture performance data related to button clicks and web requests that are triggered along my journey through this app. This enables Dynatrace to analyze application usage, improve performance, and address any troubles that may arise.
Don't include my personal data (for example, my email address) in reported data
Allow Dynatrace to collect crash reports, including stack traces and error messages. Dynatrace uses this information to resolve problems that you may encounter while using this app.