Multi-language and masking keywords per language
Co-browse works in es/en/pt and hides sensitive data via per-language keywords. How the language is chosen and which terms trigger masking.
Watch this step in the video · What the customer types stays hidden
What it is and what it's for
Omnifox co-browse works in Spanish, English and Portuguese — both the interface the customer sees (consent banner, session pill, voice call) and the automatic detector that hides sensitive data. This article explains how the language is chosen and which keywords trigger masking in each language.
How the widget picks the language
The widget resolves the language in this order:
- The
localeparameter Omnifox sends when starting the session. - If absent, the
langattribute of your<html>(e.g.<html lang="pt">). - If that's missing too, it falls back to English.
So it's worth declaring your page's language with <html lang="en"> (or es / pt): that way the customer sees "Accept/Decline", "Reconnecting…" or "Sharing screen" in the right language.
Masking keywords per language
The detector inspects each field's name, id, placeholder, aria-label, autocomplete and associated <label>. If it finds any of these terms, it masks the field automatically:
- English:
password,passwd,card,cardnumber,cvv,cvc,security code,pin,ssn,social security,passport. - Spanish:
contraseña,clave,tarjeta,numero de tarjeta,codigo de seguridad,cedula,ruc,dni,pasaporte. - Portuguese:
senha,cartao/cartão,cpf,rg.
On top of that, every <input type="password"> is always masked, regardless of language. Matching is case-insensitive (the detector lowercases everything), so Card or CARD work too.
Steps to take advantage of it
- Name your sensitive fields with one of the terms above. For example
name="card_number"or a<label>Passport</label>tied to the input. - Declare the page language with
<html lang="en">. - Start a test session and confirm in the agent view that those fields come through redacted.
Verification
- In the agent view, detected fields show up as a redacted block.
- The consent banner the customer sees should be in the expected language ("Screen sharing request" / "Solicitud de compartir pantalla" / "Pedido de compartilhar tela").
If it doesn't work
- The field isn't masked: its
name/id/labelprobably contains no keyword. Rename it, or mask it manually withdata-rrweb-mask="true"orwindow.OmnifoxCobrowse.mask('#your-field'). - The language shows in English: your
<html>is missinglang. Add it. - You have a region-specific sensitive term: don't expect the detector to guess it; mask it manually.
Tips
- Card data shown as plain text (a "Card ending in 1234" summary) is also hidden if the container has a keyword or the
data-rrweb-maskattribute. - The detector uses a MutationObserver: fields added later (modals, checkout steps) are masked as soon as they render.
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.