Hear it from the people using the product

A quiet in-app feedback tab that routes bugs to engineering and ideas to the backlog, without adding a session recorder to your application.

Product teams need a channel that is always available and costs the user almost nothing to use. Support tickets are too heavy for "this is slightly wrong", and a quarterly survey misses the moment entirely.

A persistent in-app tab captures the small reports that never become tickets — and those are frequently the ones that predict churn.

Separate bugs from ideas at intake

Enable the bug, idea, and question chips and the type prefixes the issue title. A quick label rule in your tracker splits them onto different boards without anyone triaging by hand.

Close the loop with the reporter

The email field is optional, and the "tell me when this is fixed" checkbox is opt-in. When someone does opt in, their address travels with the issue so whoever fixes it knows there is a person waiting.

Add nothing to your privacy posture

No cookies, no local storage, no session recording, no click or scroll tracking. Nothing at all is collected passively, which means adding BugLoop does not change what your privacy policy has to disclose about passive tracking.

Two things are worth knowing before you install it. A user can attach a screenshot, but only by pressing the button — the image is masked before it is taken, and they see it before it is attached. And dictation, which routes audio through the browser's speech service, is off unless you switch it on; that is the only third-party request the widget can produce.

Frequently asked

Does the widget slow down our app?
It is a single deferred script of a few kilobytes gzipped, and it makes one request on load. The screenshot library is a separate file fetched only if a user presses the button, so it costs nothing to anyone who does not. The build fails if either bundle exceeds its size budget.
Can we show it only to signed-in users?
Yes — render the script tag conditionally in your own layout. The widget has no opinion about who sees it.
Do we need a cookie banner for it?
The widget sets no cookies and writes nothing to the device, so it does not itself trigger consent requirements. Confirm your own obligations with your counsel.