Fields hidden automatically (keyword list ES/EN/PT)

The keyword list Omnifox uses to detect and hide sensitive fields in Co-browse, and how to add your own.

Jun 26, 2026

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

Co-browse's automatic masking decides which fields to hide using two rules: every <input type="password"> is always hidden, and any field whose "label text" contains a sensitive keyword is hidden too. This article lists those keywords and explains how to add your own.

How the decision is made

For each field, Omnifox builds a lowercase text fingerprint from:

  • name, id, placeholder, aria-label
  • autocomplete and data-testid
  • the text of the associated <label> (via for= or as a wrapper)

If that fingerprint contains any of the keywords (partial, case-insensitive match), the field is marked sensitive and hidden. Detection is deliberately generous: a false positive does no harm (the agent just sees a redacted block), while a false negative would leak data.

Recognized keywords

English: password, passwd, card, cardnumber, card_number, cardno, cvv, cvc, cvc2, security code, pin, ssn, social security, passport.

Spanish: contraseña, contrasena, clave, tarjeta, numero de tarjeta, codigo de seguridad, codigo de verificacion, cédula, cedula, ruc, dni, pasaporte.

Portuguese: senha, cartao, cartão, cpf, rg.

Accented and unaccented variants are both included (cédula/cedula, cartão/cartao) to cover how different sites name their fields.

Fields that appear later

Detection isn't only at startup: Omnifox watches the page and re-evaluates when new fields are added or attributes like type, name or placeholder change. So a form that loads in a modal dialog, or after navigating within the same page, is covered too.

How to add your own fields

If a sensitive field matches no keyword (for example, a field named in another language, or a custom widget), you have two options:

  1. Rename the field so its name, id or label includes a keyword from the list.
  2. Mark it manually from the site:
window.OmnifoxCobrowse.mask('#secret-field');

You can also add the attribute data-rrweb-mask="true" directly on the field's HTML.

Verification

Start a test session and open the form in question. On the agent side, the sensitive field should appear redacted. If it isn't hidden, check that its name/id/label contains a keyword, or add it manually with the method above.

Tip

When you design new forms, naming payment or ID fields with standard terms (card, cvv, cedula, cpf) makes masking work with no extra steps.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp