Skip to main content

Configure capture controls and privacy

Use this guide to tune replay fidelity while protecting sensitive data.

Start from a safe baseline​

import { browser } from '@oxvo/browser';

browser.configure({
  workspaceId: 'YOUR_WORKSPACE_ID',
  maskTextEmails: true,
  maskTextNumbers: true,
  inputPrivacyMode: 1,
  networkCapture: {
    enabled: true,
    captureBodies: false,
    ignoreHeaders: ['cookie', 'set-cookie', 'authorization'],
  },
});

This configuration keeps capture useful while reducing sensitive payload exposure.

Control input and text masking​

  • maskTextEmails: masks email-looking text nodes.
  • maskTextNumbers: masks numeric characters in text nodes.
  • inputPrivacyMode: controls input value masking behavior.
browser.configure({
  workspaceId: 'YOUR_WORKSPACE_ID',
  maskTextEmails: true,
  maskTextNumbers: false,
  inputPrivacyMode: 1,
});

Use stricter settings on auth, billing, and healthcare flows.

Mark sensitive DOM regions with attributes​

Use element-level controls directly in markup:

<div data-oxvosessions-hidden>
  Entire block is hidden from replay output
</div>

<div data-oxvosessions-obscured>
  Visible shape is kept, text is masked
</div>

<input data-oxvosessions-obscured />
  • data-oxvosessions-hidden: remove subtree content from replay rendering.
  • data-oxvosessions-obscured: keep layout, mask textual details.

Use private-by-default mode​

For high-sensitivity applications, mask all DOM by default and opt-in safe regions:

browser.configure({
  workspaceId: 'YOUR_WORKSPACE_ID',
  maskAllByDefault: true,
});

Then selectively unmask safe elements:

<section data-oxvosessions-unmask>
  Product catalog content safe for replay
</section>

Warning: maskAllByDefault can reduce debugging value if you do not explicitly unmask key UI areas.

Apply rule-based DOM sanitization​

Use domSanitizer when you need deterministic masking by selector, role, or class:

import { browser, SanitizeLevel } from '@oxvo/browser';

browser.configure({
  workspaceId: 'YOUR_WORKSPACE_ID',
  domSanitizer: node => {
    if (node.matches('.payment-card, .ssn, [data-pii]')) {
      return SanitizeLevel.Obscured;
    }
    if (node.matches('.security-answer, .secret-token')) {
      return SanitizeLevel.Hidden;
    }
    return SanitizeLevel.Plain;
  },
});

SanitizeLevel.Hidden is stricter than Obscured and should be used for irreversible secrets.

Tune network payload capture​

browser.configure({
  workspaceId: 'YOUR_WORKSPACE_ID',
  networkCapture: {
    enabled: true,
    captureBodies: false,
    failuresOnly: false,
    sessionTokenHeader: 'X-OXVO-Session',
    ignoreHeaders: ['cookie', 'set-cookie', 'authorization'],
  },
});

Recommended defaults:

  • Keep captureBodies: false unless you have explicit approval.
  • Keep auth/session headers in ignoreHeaders.
  • Prefer endpoint-level sanitization over broad body capture.

Privacy verification checklist​

  1. Trigger a full critical user journey in staging.
  2. Confirm replay visibility for layout and interactions.
  3. Confirm secrets are masked or hidden in replay.
  4. Confirm network payloads follow your redaction policy.
  5. Review with security/compliance before production rollout.

📷 Image (optional): Privacy controls before-and-after replay output
Why: Helps teams validate that masking and hidden rules work as intended without losing critical troubleshooting context.
File: docs/images/sdk-sessions-privacy-controls-before-after.png
AI prompt: "Clean documentation comparison mock for OXVO replay UI showing side-by-side before and after privacy rules, with masked text fields, hidden secure blocks, and sanitized network panel, modern SaaS style, neutral background, crisp typography, synthetic labels only, no personal data, 1600x1000."