BugMojoBugMojo
Get started
How-to

Verify redaction yourself in DevTools

Prove that BugMojo masks your data by watching the actual capture payload leave your browser.

Applies toPlans:FreeProBusinessEnterpriseWhere:ExtensionWeb app

You do not have to take our word that redaction works. Because masking runs in your browser before a capture is uploaded, you can open your browser's own DevTools, watch the request go out, and read the exact data BugMojo receives. This how-to walks you through it in a couple of minutes.

What you'll need

Before you start, make sure you have:

  • The BugMojo extension installed and signed in.
  • A page open where you can trigger a real capture.
  • Your browser's built-in DevTools (no extra tools required).

Watch the payload leave your browser

  1. Open the page where you want to capture a bug. Press F12 (or right-click and choose Inspect) to open DevTools, then click the Network tab.

  2. Filter the list to Fetch/XHR so you only see API calls, and tick Preserve log so the request stays visible after the page updates.

  3. Type something sensitive into a form on the page (for example a fake password or email) so you have real input to check for later.

  4. Capture the bug as normal: click the BugMojo extension icon and submit the report.

  5. In the Network list, find the outgoing POST upload to www.bugmojo.com (the BugMojo API) and click it.

  6. Open the Payload (or Request) tab to see the raw JSON. Scroll the session replay events and search for the text you typed. You will find it masked with asterisks or blanked out, not in the clear.

What masked data looks like

In the payload, text nodes and input values are replaced with placeholder characters (usually asterisks like ****) or left empty. The structure of the page is preserved so the replay is still useful for debugging, but the characters you typed are gone. This is client-side redaction in action: the masking happens at the source, on your device, before the request is assembled.

Common questions

Which request shows the capture being uploaded?

Look for the POST request to the BugMojo API on www.bugmojo.com. Open its Payload tab to read the exact JSON your browser is sending.

Will I see my passwords or typed text in the payload?

No. Input values and text are masked in your browser before the request is built, so you will only see asterisks or blanks, never the real characters.

Does this work in any browser?

Yes, in any browser the extension runs in. Chrome, Edge, and other Chromium browsers all ship DevTools, and the Network tab shows the same outgoing capture payload.

Was this helpful?
Updated Jul 10, 2026 · Still stuck? Contact support

Related articles