DataDog
diff --git a/‎content/en/data_security/real_user_monitoring.md
Lines changed: 9 additions & 9 deletions b/‎content/en/data_security/real_user_monitoring.md
Lines changed: 9 additions & 9 deletions
diff --git a/‎static/images/data_security/data-security-rum-privacy-compliance-user-data-collection-1.png
180 KB b/‎static/images/data_security/data-security-rum-privacy-compliance-user-data-collection-1.png
180 KB
@@ -50,7 +50,7 @@ By default, there are some privacy restrictions in place that protect user data
 Browser RUM requires first party cookies to be enabled on an end user's browser to collect data. If required by the jurisdictions in which you operate, you are responsible for configuring your pages to comply with the laws of those jurisdictions, including receiving consent to collect cookies before RUM is initialized.
 
 ### Mobile RUM consent management
-Mobile RUM tracking is only run upon user consent. If the end user accepts the RUM tracking, we track their activity and session experience. If the user declines the RUM tracking, we do not track their activity and session experience.
+Mobile RUM tracking is only run upon user consent. If the end user accepts the RUM tracking, Datadog tracks their activity and session experience. If the user declines the RUM tracking, Datadog does not track their activity and session experience.
 
 ## Privacy options
 You have several options and tools when it comes to collecting and redacting data captured by RUM.
@@ -69,7 +69,7 @@ One method of using the client token to filter out bots is an authenticated prox
 The proxy is configured to check for valid user information before passing the session data to Datadog, thereby confirming that a real user is signed in and transmitting traffic to be monitored. When receiving traffic, the proxy verifies that the data includes the placeholder string and replaces it with the real `clientToken` before forwarding the data to Datadog.
 
 ### Event tracking
-An [event][5] is a user interaction with specific elements of your site or app. Events can be automatically captured via the SDK or sent via custom actions. You can turn off automatic tracking of user interactions and page views to only capture the interaction of your choice. By default, RUM uses target content to generate action names from actions automatically collected by the SDK. You can [explicitly override][6] this behavior with any given name.
+An [event][5] is a user interaction with specific elements of your site or app. Events can be automatically captured through the SDK or sent through custom actions. You can turn off automatic tracking of user interactions and pageviews to only capture the interaction of your choice. By default, RUM uses target content to generate action names from actions automatically collected by the SDK. You can [explicitly override][6] this behavior with any given name.
 
 The data we track automatically contains primarily technical information, much of which doesn't include personal identifying information. Data that is captured by RUM can be further redacted before it is sent and stored in Datadog through advanced configuration options for the following methods:
 
@@ -99,7 +99,7 @@ To extend your data retention for analyzing user behaviors over longer time peri
 Datadog provides role-based access control (RBAC) for managing who sees captured RUM data. Default settings for data access depend on the role a user gets added to. There are three types of Datadog roles available: Administrator, Standard, and Read Only 
8000
roles. More granular RUM-specific permissions are defined in [Datadog role permissions][15]. For example, you can grant or revoke access to view Session Replays.
 
 ### Data deletion
-If you need to delete data stored by Datadog, for example, if potentially sensitive data has been leaked into RUM events, you can hard-delete data from within a given timeframe. With a hard delete, **all** data is deleted; it cannot be targeted to a specific application. If you need any data deleted, reach out to the [Datadog support team][14].
+If you need to delete data stored by Datadog, for example, if potentially sensitive data has been leaked into RUM events, you can hard-delete data from within a given time frame. With a hard delete, **all** data is deleted; it cannot be targeted to a specific application. If you need any data deleted, reach out to the [Datadog support team][14].
 
 ### Personal and sensitive data removal
 You have some options available for removing Personally Identifiable Information (PII), and sensitive data, including IP addresses and geolocation. Some scenarios where PII could appear in RUM:
@@ -112,21 +112,21 @@ You have some options available for removing Personally Identifiable Information
 By default, if you wish to mask all action names, you can use the `enablePrivacyForActionName` option in conjunction with the `mask` privacy setting. This operation automatically substitutes all non-overridden action names with the placeholder `Masked Element`. This setting is also designed to be compatible with existing [HTML override attributes][16].
 
 #### Unstructured data
-PII inadvertently included in unstructured data, such as an individual's name in a text box, can only be removed through a data deletion requisition for a specified timeframe.
+PII inadvertently included in unstructured data, such as an individual's name in a text box, can only be removed through a data deletion requisition for a specified time frame.
 
-With respect to URLs, you have the option to track page views manually in order to remove any PII or use beforeSend to change the URL text.
+With respect to URLs, you have the option to track pageviews manually to remove any PII or use beforeSend to change the URL text.
 
 You can also transmit all RUM events through your own (proxy) server so that end user devices never directly communicate with Datadog.
 
 #### IP address
-When setting up a RUM application, you can choose whether or not you want to include IP or geolocation data:
+After you've initialized 
8000
your RUM application, you can choose whether or not you want to include IP or geolocation data from the **User Data Collection** tab:
 
-{{< img src="data_security/data-security-rum-privacy-compliance-edit-rum-application.png" alt="You can include or exclude geolocation and client IP data from the RUM application setup page" style="width:100%;" >}}
+{{< img src="data_security/data-security-rum-privacy-compliance-user-data-collection-1.png" alt="You can include or exclude geolocation and client IP data from the RUM application management page" style="width:100%;" >}}
 
-Once you disable collection of IP data, the change will be applied immediately. Any events collected prior to disabling will not have their IP data removed. It is performed on the backend, which means the Browser SDK will still be sending data, but IP addresses will be omitted by Datadog backend pipelines and dropped at processing time.
+After you disable the collection of IP data, the change is applied immediately. Any events collected prior to disabling does not remove the IP data. It is performed on the backend, which means the Browser SDK is still sending data, but IP addresses are omitted by Datadog backend pipelines and dropped at processing time.
 
 #### Geolocation
-In addition to removing client IPs, you can also choose to disable the collection of geolocation (country, city, county), or GeoIP, from all future collected data. If you uncheck the **Collect geolocation data** box, the change will be applied immediately. Any events collected prior to disabling will not have their geolocation data removed. Data omission is done at the backend level, which means the Browser SDK will still be sending data, but geolocation data will be omitted by our backend pipelines and dropped at processing time.
+In addition to removing client IPs, you can also choose to disable the collection of geolocation (country, city, county), or GeoIP, from all future collected data. If you uncheck the **Collect geolocation data** box, the change is applied immediately. Any events collected prior to disabling does not remove corresponding geolocation data. Data omission is done at the backend level, which means the Browser SDK is still sending data, but geolocation data is omitted by Datadog backend pipelines and dropped at processing time.
 
 ### Proactively search for sensitive data with Sensitive Data Scanner
 [Sensitive Data Scanner][17] allows you to proactively search and scrub sensitive data upon ingestion by Datadog. RUM events are scanned on the stream before any data is stored within Datadog. The tool has the power to scrub, hash, or partially redact PII data before it is stored. It works by applying out-of-the-box or customer-developed pattern matching rules. If you've enabled this feature, you can find it on the [**Manage Sensitive Data** page][18].