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.
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-labelautocompleteanddata-testid- the text of the associated
<label>(viafor=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:
- Rename the field so its
name,idorlabelincludes a keyword from the list. - 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
Related articles
-
What Co-browse is and how to enable it
Co-browse lets you see the customer's screen in real time to guide them better. Learn how to enable it.
-
Co-browse complete guide
Co-browse in depth, in 32 chapters: radar, identified visitors, consent, remote control, masking, marks, voice call, page changes and how a session ends, all real.
-
Co-browse: add-on tiers and pricing
Co-browse is bought separately on any plan: Standard 50 USD/mo (3 concurrent sessions), Pro 90 (6), Business 150 (10) and custom Enterprise.
-
How to start a Co-browse session with a customer
Step by step to invite the customer to share their screen and guide them in real time.
-
Prerequisites for using Co-browse
Before you start your first Co-browse session, check the add-on, your permissions and the Webchat channel conditions.