Redact PII on the client before it leaves the browser

When you capture a bug, the extension records the DOM, your inputs, and network traffic. Some of that can hold personal data: names, emails, card numbers. BugMojo handles this by masking sensitive content in the browser, before a report is ever uploaded. This page shows what is masked by default and how to adjust the rules for your app.

Out of the box, capture masks the content that most often carries personal data, so you are covered before you change any setting:

• Input values: text you type into fields is replaced with placeholder characters, so passwords, emails, and card numbers are never recorded as typed.
• Password fields: always masked and never sent in the clear.
• Authorization headers: bearer and basic auth values are masked at capture time.

Screenshots capture what is on screen, so review and annotate them before you share. Network request and response bodies are never captured. Only the URL, method, status, and timing are recorded. See what BugMojo cannot capture for the full picture.

The extension masks inputs, password fields, and auth headers by default and requires no configuration. For the embeddable widget/SDK, an owner or admin can tighten the policy per board from the dashboard. This is where CSS-selector tuning and the organization floor live.