Co-browse Privacy: What Is Shared and What Is Never Recorded

Co-browse lets an agent see — and, if the customer allows it, interact with — whatever screen the visitor has open in the Webchat widget. Since it's a real live screen share, it's fair to ask exactly how exposed the customer's data is.

What gets shared

• Only the visual content of the Webchat page: text, buttons, images, and styling, live, for the duration of the session.
• The agent's mouse movements, scrolling, and clicks, if the customer enabled remote control.

What is NOT shared or recorded

• Form fields are masked by default: passwords, plain text, emails, phone numbers, and numeric fields all show as dots (●●●●) from the very first frame, before mirroring even starts.
• <canvas>, video, and audio elements are never captured: the agent sees an empty placeholder instead of the actual content.
• Nothing is saved as a recording: the screen is streamed live, directly between the customer's browser and the agent's over the real-time channel. Omnifox doesn't store the session's video for later playback — only metadata (who participated, when it started and ended, and why) is kept.

Consent is mandatory

The session never starts until the visitor explicitly accepts the screen-share request. No "Yes," no stream.

Example

A customer fills out a payment form while an agent guides them via Co-browse. The agent sees the page layout and where the customer clicks, but the card-number field always shows as dots, never as plain text.

Tips

• If you need a specific field NOT to be masked (say, a public field with no sensitive data), that's configured on the customer's own site, not from Omnifox.
• Even though nothing is recorded, an audit trail of when Co-browse was used and with whom is still kept.