Skip to content
BugCapturer BugCapturer Docs

Privacy red lines

BugCapturer puts user privacy and data security first in product design. A feedback tool that embeds into your site and runs in your end users’ browsers has to earn that trust with verifiable technical boundaries. So what follows is not a “best effort” promise, but privacy red lines baked into the implementation — guaranteed by design rather than by good intentions.

What we deliberately never collect

Section titled “What we deliberately never collect”
  • No reading of the host page’s cookies / localStorage — the embedded Web SDK never inspects a visitor’s session on your site to “guess” identity. Reporter identity must be passed in explicitly by your site: see Reporter identity
  • No keystroke logging — only the description text a visitor deliberately submits
  • Nothing beyond the current page — screen recording covers the current tab only; other tabs and your browsing history are untouched
  • No behavioural tracking or ad profiling — no user profiles, no cross-site tracking, no selling of data

Automatic URL masking

Section titled “Automatic URL masking”

Page addresses often carry sensitive parameters (session credentials, temporary tokens). Before a report is sent, parameters such as token, key and password are replaced with *** and only then written into the report.

This happens automatically and by default — there is nothing to remember to check.

Uploads are always triggered by you

Section titled “Uploads are always triggered by you”
  • Screenshots, annotations, recordings, editing and exporting are all local and offline
  • Content is uploaded only when you click “Share” or “Submit”
  • Share links are randomly generated and unguessable, and are not indexed by search engines

You can delete at any time

Section titled “You can delete at any time”
  • Every share can be deleted from the console, effective immediately
  • Expired content is deleted automatically (30 days anonymous / 90 days signed-in / long-term on paid plans)