Masking
What is masked before anything leaves the page, and the attributes that change it.
On this page
Masking happens in the browser, before anything is sent, and the gateway repeats parts of it on arrival, as noted below.
Text the browser part reads
The browser part reads very little text: the label and accessible name of a control that is clicked (at most 60 and 80 characters), and field names and attributes. Text is read only from real buttons, submit inputs and simple links. In all of it:
| Found | Sent as |
|---|---|
| An email address | [email] |
| A phone number (a run of digits, spaces and punctuation, 9 characters or more) | [number] |
| Any other run of four or more digits | # |
So a button labelled "Email jane@example.com" is sent as "Email [email]", and an order number in a link label never leaves the page.
Up to version 1.0.3, a click on a link or button that wraps a larger block (an address card, say) also sent that block's text as the control's name, at most 80 characters with the masking above; since October 16, 2026 Parlox drops it on arrival, and version 1.0.4 no longer sends it.
Field names, element ids and classes, and link paths are sent as your markup has them (link paths with the path token rule below).
Field values are never read at all: not masked, simply not read. Only a field's name, type and autocomplete attribute are.
Addresses
- Path tokens. A path segment of 20 or more letters and digits containing both, or a UUID, is replaced with
:token, as are account reset and activation links. These are the capability tokens in checkout, order and reset links. Hyphenated segments such as product slugs are kept. - Query strings. Only campaign parameters are kept (
utm_source,utm_medium,utm_campaign,utm_content,utm_term,ref,gclid,fbclid,srsltid, each cut to 120 characters). Everything else, search terms included, is dropped. - Referrers. Another site's referrer is reduced to its origin (
https://chatgpt.com/); your own site's gets the path token rule.
The gateway applies the path token rule again before it stores anything.
Recordings
Agent recordings are private by default:
- every input a visitor can type into is masked, always;
- every text node is masked, character by character, except the label of a real control, which gets the masking above;
- hidden form fields and link, image and form addresses are rewritten by the address rules above, and the page address in a recording keeps only its path and campaign parameters (on arrival since October 16, 2026; in the recorder from 1.0.4);
- iframes are left out.
You can widen or narrow that, element by element:
| Attribute | Effect |
|---|---|
data-plx-unmask | Text inside is recorded as it is (product details, for example) |
data-plx-mask | Everything inside is masked, control labels included |
data-plx-block | The element is left out of the recording entirely |
These attributes affect recordings only. Inputs a visitor can type into stay masked inside data-plx-unmask too.
Commerce events
Only item_id, value, currency, items, order_id and step are kept from a commerce event, whatever else is sent with it. Names, emails and addresses are dropped by the browser part and again by the gateway.