Explainer

Disclose the BugMojo widget to your visitors

What the always-on widget buffer does, when data is uploaded, and copy you can paste into your own privacy policy.

Applies toPlans:FreeProBusinessEnterpriseWhere:Web app

The BugMojo widget lets your users report a bug with full context — a session replay, console logs, and network metadata — without you having to reproduce it. Because that context has to exist before the user decides to report, the widget maintains a short in-memory buffer while capture is enabled. This article explains exactly what that means, and gives you copy you can drop into your own privacy policy to disclose it to your visitors.

How the rolling buffer works

Once the widget loads and confirms that bug capture is enabled for the current environment (and any sampling and login rules allow it), it warms up a rolling buffer in the background during an idle moment. The buffer holds only the most recent activity — it is designed to give a report a few seconds of history, not to record an entire session indefinitely.

Crucially, this buffer is local. It is never written to disk and never sent to BugMojo on its own. The upload happens at exactly one moment: when a visitor opens the reporter, fills it in, and submits. Before that payload leaves the browser, redaction runs — input values are masked, authorization headers are masked, PII and secrets are scrubbed, and network request and response bodies are never included at all.

You stay in control of capture

Capture is governed by remote configuration, so you never need a code change to adjust it:

Per-environment: enable capture in development or staging but not production, or anywhere you choose.
Sampling: record a fraction of sessions with a deterministic sample rate.
Kill switch: turn capture off for a project/environment from the dashboard at any time.
Login gating: require a logged-in reporter, so anonymous visitors are not captured.

How this differs from the browser extension

The widget is embedded by you into your own site, so you are the controller and it is your responsibility to disclose it to your visitors — hence the language below. The browser extension is different: it is installed by an individual on their own device, requires an explicit consent step before it captures, and only records when that person starts a capture. The extension does not maintain an always-on buffer for your site's visitors.

Suggested privacy-policy language

Adapt the following to your site and add it to your privacy policy or cookie notice. Replace bracketed text. This is a starting point, not legal advice — have your own counsel review it.

text

Bug reporting and diagnostics

We use BugMojo, a third-party bug-reporting tool, to help us diagnose and fix
problems on [YOUR SITE]. When bug reporting is active, BugMojo keeps a short,
in-memory record of recent on-page activity (a reconstruction of the page and
console/network diagnostics) so that if you choose to report a problem, we
receive enough context to fix it.

This information stays in your browser and is only sent to us if you submit a
bug report. Sensitive data is minimized before it is sent: form inputs are
masked, and the content (bodies) of network requests is never collected.

We use this data solely to diagnose and resolve technical issues. It is
processed by BugMojo on our behalf under a data processing agreement. For more
information, see BugMojo's privacy and security documentation, or contact us at
[YOUR CONTACT].

Common questions

Does the widget record every visitor all the time?

When bug capture is enabled for that environment, the widget keeps a short in-memory rolling buffer so a report has recent context. Nothing is uploaded unless a user actually submits a report.

Where does the buffered data live before a report is sent?

In the visitor's browser memory only. It is not persisted and not transmitted to BugMojo until the moment a report is submitted, at which point redaction has already run in the browser.

Can I turn capture off for production?

Yes. Capture is governed by remote config — you choose the enabled environments, set a sample rate, or flip the kill switch from the dashboard without changing any code.

Do I need to tell my visitors?

If you enable the widget on pages your visitors see, you are the controller for that capture. We provide suggested privacy-policy language below so you can disclose it clearly.

Was this helpful?

Updated Jul 24, 2026 · Still stuck? Contact support