---
title: "Configuring Information Security & PII"
slug: "cobrowse-configuring-information-security-pii"
description: "Learn how to protect sensitive information during cobrowsing by using HTML attributes and classes to exclude confidential elements from sharing."
updated: 2022-08-04T11:51:48Z
published: 2022-08-04T11:51:48Z
canonical: "docs.screenmeet.com/cobrowse-configuring-information-security-pii"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Information Security & PII

Any input or element on a page which contains sensitive information which should not be shared with the cobrowsing agent the following html attribute or class should be added.

*!*Password fields are always excluded by default.

```markup
<input type="string" id="credit-card-number" data-cb-mask="true" /> <div id="accountnumber" data-cb-mask="true">23434645631234523</div>
```

or

```markup
<input type="string" id="credit-card-number" class="cb-mask" /> <div id="accountnumber" class="cb-mask">23434645631234523</div>
```

Fields or elements with these designations will not be sent to the ScreenMeet’s server and any input or changes to these elements AND child elements will also not be sent. There will be an overlay added to confidential elements to let the clients know that those elements are not shared with the agent. If sensitive elements in the page already marked with a class or an attribute Cobrowse can be configured to exclude them as well. Here is an example.

```javascript
window.Cobrowse = window.Cobrowse || {};
window.Cobrowse.modal = window.Cobrowse.modal || {
  commandQueue: [], 
  confidentialMasks: ['pii', 'data-pii']
};
```

The specification of the customizable masks (using TypeScript interface and type declarations):  
  
  

```typescript
interface Window {
  Cobrowse: {
    modal: {
      confidentialMasks: string[]
      ...
    }
  }
}
```