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.

Jun 26, 2026

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:

  1. The locale parameter Omnifox sends when starting the session.
  2. If absent, the lang attribute of your <html> (e.g. <html lang="pt">).
  3. 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

  1. Name your sensitive fields with one of the terms above. For example name="card_number" or a <label>Passport</label> tied to the input.
  2. Declare the page language with <html lang="en">.
  3. 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/label probably contains no keyword. Rename it, or mask it manually with data-rrweb-mask="true" or window.OmnifoxCobrowse.mask('#your-field').
  • The language shows in English: your <html> is missing lang. 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-mask attribute.
  • The detector uses a MutationObserver: fields added later (modals, checkout steps) are masked as soon as they render.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp