Sensitive data hiding

When using native rendering mode, SDK can record sensitive data in your application.

In order to protect user privacy, Smartlook can be configured so that the sensitive data is not recorded.

📘

Sensitive elements are hidden locally on the device. No sensitive data are transferred over the network and stored in the dashboard.

Hidden elements

Sensitive elements can be blacklisted by marking them with .smartlook-hide css class:

<div class='smartlook-hide'>
   This will be hidden.
</div>

🚧

All inputs are hidden by default except for button and submit types.

Shown elements

Hidden inputs that are hidden by default will be recorded if marked with .smartlook-show css class:

<input type="text" class='smartlook-show'>

No Rendering

Sometimes the whole screen consists of sensitive data. In these cases it is beneficial to not record any screen data. This can be done by switching to no rendering rendering mode:

Smartlook.setRenderingMode({renderingMode: Smartlook.RenderingMode.NO_RENDERING})

🚧

Some screens can leak sensitive data even through automatically detected touch events. More about this issue in secure custom keyboard example.

When an application is no longer displaying sensitive data, the screen rendering mode can be set back to the preferred variant:

Smartlook.setRenderingMode({renderingMode: Smartlook.RenderingMode.NATIVE})