Ensuring the privacy of your customers' personal data is now a key component of your digital business success. Dynatrace provides numerous privacy enhancements that make it easy for you to configure appropriate settings that protect your customers' personal data and ensure your organization's compliance with GDPR or other data privacy regulations.
For details on the global data privacy settings, see Configure data privacy settings.
To access the data privacy settings for your web application
On this page, the following settings are available:
Check the sections below for the detailed description of each setting.
To access this option, select General settings > Data privacy > General from the application settings.
🔴 Disabled by default
Dynatrace captures full URIs of requests that are sent from desktop and mobile browsers, as well as URIs of requests that are sent and received within monitored server-side processes. URIs may contain personal data, such as a user name, password, or ID.
When Mask personal data in URIs is turned on, Dynatrace detects personal data—emails, IBANs, payment card numbers, IP addresses, UUIDs, and other IDs—in URIs, query strings, headers, exception messages, and data captured for request attributes and replaces this data with the <masked> string (for example, /url?country=Austria&city=Linz changes to /url?country=<masked>&city=<masked> and /account/iban('123456678890') changes to /account/iban('<masked>')). As a result, the personal data is then masked in the distributed trace analysis, error analysis, user action names for RUM, and elsewhere in Dynatrace.
To access this option, select General settings > Data privacy > General from the application settings.
🔴 Disabled by default
The Mask user actions (web applications only) option affects Real User Monitoring only for web applications. With this option enabled, Dynatrace uses generic values for user action names.
When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:
click on..., loading of page..., or keypress on...In most instances, the default approach to user action naming works well, resulting in user action names such as:
click on "Search" on page /search.htmlkeypress on "Feedback" on page /contact.htmltouch on "Homescreen" of page /list.jsfIn rare circumstances, email addresses, usernames, or other confidential data may be unintentionally included in user action names. This happens when confidential data is included in an HTML element label, attribute, or other value, resulting in user action names such as click on "My Account Number: 1231231". If such confidential data appears in your application's user action names, turn on Mask user actions (web applications only) . This setting replaces specific HTML element names and values with generic HTML element names.
With user action name masking enabled, the user action names listed above appear as:
click on INPUT on page /search.htmlkeypress on TEXTAREA on page /contact.htmltouch on DIV of page /list.jsfTo access this option, select General settings > Data privacy > General from the application settings.
🔴 Disabled by default
The Use persistent cookies for user tracking setting allows you to enable or disable the use of persistent cookies that detect and track returning users.
When turned on, Real User Monitoring sets a persistent cookie in end-user browsers that detects if the browser has been used previously to access your application. When turned off, Dynatrace is no longer able to correlate anonymous user sessions with tagged user sessions, so the Returning vs. new users RUM metric no longer works. Learn how we store this cookie.
User tracking is disabled by default for all newly created applications. Settings for existing applications aren't affected, so you must configure them manually.
To access this option, select General settings > Data privacy > General from the application settings.
🔴 Disabled by default
To provide your end users with the ability to decide for themselves if their activities should be tracked or not (this is called "cookie opt-out capability"), enable the opt-in mode.
Usually, Dynatrace creates tracking cookies automatically. When Data-collection and opt-in mode is turned on, RUM is disabled and no cookies are created. When an end user accepts your cookie policy, Dynatrace enables RUM and sets the tracking cookies.
For web applications, the injected RUM JavaScript doesn't capture any data or set cookies when the opt-in mode is enabled. After your end user accepts your cookie policy, you can activate RUM for this particular user via the dtrum.enable() JavaScript API call.
Dynatrace also provides an API call that can disable monitoring after you've activated it via the dtrum.enable() API call. Using the dtrum.disable() API call, you can implement a dialog that allows your end users to stop sending monitoring data to Dynatrace even after they've agreed to it before.
To access this option, select General settings > Data privacy > General from the application settings.
🟢 Enabled by default
Another technique for protecting end-user privacy is the "Do Not Track" feature. When a user enables this feature, their browser adds the DNT HTTP request header to all outgoing web requests. This header specifies that all user tracking must be disabled.
After you turn on Comply with "Do Not Track" browser settings, you can select between two options:
DNT header is detected, Dynatrace captures RUM data but excludes all personal information that could lead to the identification of the user. The IP address is masked, and no user tag information is sent.
With the User tracking setting enabled, Dynatrace still sets a persistent cookie to detect returning users.
DNT header is detected, Dynatrace doesn't capture any data from browsers that have the "Do Not Track" setting enabled.If you turn off Comply with "Do Not Track" browser settings, Dynatrace ignores the browser's "Do Not Track" setting and the DNT header.
The Comply with "Do Not Track" browser settings — Capture anonymous user sessions for "Do Not Track"-enabled browsers option is enabled by default for all environments and applications.
To access this option, select General settings > Data privacy > General > IP masking from the application settings.
🟢 Enabled by default
Dynatrace captures IP addresses and GPS coordinates of end users to determine the region from which they access your application.
With the Mask end-user IP addresses and GPS coordinates option turned on, Dynatrace masks end user IP addresses and GPS coordinates during Real User Monitoring and server-side monitoring. The last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses are replaced with zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). The masking occurs within the application, monitored process, or browser so that the data is already masked before it's sent (data in transit) to the Dynatrace cluster. Location lookups are made using anonymized IP addresses and GPS coordinates.
The Mask end-user IP addresses and GPS coordinates — Mask all IP addresses option is enabled by default for new environments.
For mobile applications, Dynatrace uses the coordinates from the device by using GPS or Wi-Fi. If the application has the permission to use this geolocation information, Dynatrace uses it to calculate the city that is closest to the reported GPS location. If not, Dynatrace uses MaxMind Geo2 Database.