I worked at a privacy company before starting this. Compliance wasn't optional, it was the lowest bar we'd accept. Every field we stored had a reason. Every record we processed got reviewed. The defaults were paranoid in a good way.
When I started looking at the tooling the rest of the SaaS world uses to triage bugs, the contrast was jarring. Session-replay platforms hoover up entire user sessions. Error monitors capture stack traces full of user data. Analytics pipes log everything by default. The mental model everywhere is "record now, redact later." Even when that's legal, it didn't sit right with me.
Here's the thing about data you collect: you're now responsible for it. Storage you fill is storage that can leak. Records you log can be subpoenaed. The more you keep, the bigger the target you become. Why take on that exposure if you don't have to?
BugJar is the answer I wanted to exist. Instead of recording everything in the background, the user clicks a button when something goes wrong. They reproduce the bug, narrate it, draw on the page if they want. They review what's about to be sent. They hit Send. Or they cancel and nothing uploads.
Sensitive fields get masked in the browser before anything reaches our servers. The upload goes directly to storage, our application never sees the contents. Even our own staff can't view the recording. That's enforced in code, not just policy.
That's the whole product. The technology is the easy part. The hard part is shipping something deliberately less aggressive than the competition and betting that customers who actually read security docs will see the difference and care.
Rulian from Wonderful Software, founder