[Live Webinar] Next-Level O11y: Why Every DevOps Team Needs a RUM Strategy Register today!

Back to All Docs

Data Masking

Last Updated: Apr. 17, 2024

Censure fields in your RUM logs with data masking to safeguard end-user privacy and prevent sensitive data collection.


Coralogix offers privacy features to safeguard sensitive or personal data for organizations of all sizes as part of Real User Monitoring. Mask sensitive elements and fields in your RUM logs via the RUM Browser SDK. This masking ensures that the Coralogix SDK does not capture sensitive data and that it is consequently not transmitted to the backend.

Masked elements will appear in your UI as stars in the log text.


User interactions with specific elements can be masked to prevent sensitive data exposure.

Use maskInputTypes to specify the types of inputs to mask. This defaults to ['password', 'email', 'tel']. Define any input and modify as desired.

Use maskClass to specify the class name used to mask any element, string, or RegExp. The default is cx-mask.

  // ...
  maskInputTypes: ['password', 'date'], // will only mask password and date inputs
  maskClass: 'mask-me' // will mask any element with class 'mask-me'


Need help?

Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.

Feel free to reach out to us via our in-app chat or by emailing [email protected].

On this page

Live Webinar
Next-Level O11y: Why Every DevOps Team Needs a RUM Strategy
April 30th at 12pm ET | 6pm CET
Save my Seat