How sensitive data is protected (automatic masking)

During Co-browse, the customer's sensitive fields are hidden automatically. Here's how the masking works and what each side controls.

Jun 26, 2026

Watch this step in the video · What the customer types stays hidden

When you share a screen with a customer through Co-browse, the last thing you want to see is their password or card number. That's why Omnifox masks sensitive data automatically, with no setup needed from you or the customer.

What "masked" means

The agent sees the customer's page, but sensitive fields appear redacted (dots or blocks instead of the real value). This isn't an after-the-fact blur: masking is turned on before streaming begins, so not even the first frame of the session carries the real data.

What's protected by default

  • Every form field: by default, any value the customer types into an input or textarea is streamed masked. It's the safest posture.
  • Password fields: any <input type="password"> is always hidden.
  • Fields detected as sensitive: cards, ID documents, security codes and passwords are recognized by keywords in Spanish, English and Portuguese, and hidden automatically — including the field's visible text, not just what's typed.

Real-time protection

Modern pages change without reloading (modal dialogs, checkout steps, autocomplete). Omnifox watches the page continuously, so fields that appear after the session starts are masked instantly too.

The agent can't type into hidden fields

Co-browse lets the agent help fill in forms remotely, but for safety the agent can never type into a masked field. The customer's password or card is theirs alone.

The customer is always in control

  • The customer accepts the session before sharing begins.
  • They can stop sharing at any time from their own widget.
  • The customer's prompt makes it clear that passwords and card data are masked automatically.

For sites with custom fields

If your site uses custom widgets for sensitive data that don't fall into the usual categories, the site owner can mark them manually with:

window.OmnifoxCobrowse.mask('#my-custom-field');

This adds those fields to the hidden list.

Verify it's working

Start a test session, open a form with a password field, and confirm it appears redacted on the agent side. If a sensitive field isn't hidden, it probably doesn't match any keyword — check the keyword article to add it.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp