Quick answers, straight from the engineers who built it.

Yes. Capturing, analyzing, exporting, importing and replaying all run free and no account is required, you can install the extension and start recording in under a minute. A free webQsee account raises the local gallery cap, lifts the 70-second limit on importing someone else's Behavior Report, and unlocks a one-time 7-day trial of webQsee-provided cloud storage (up to 5 items). Paid plans cover longer recordings (5 minutes on Pro, 15 on a team plan, against 1 minute free), an AI that reads the recording for you with nothing to set up, a permanent Cloud Gallery with higher item caps and a 1-year lifetime, bring-your-own Amazon S3 / min.io, downloads without the webQsee badge, and team features like shared settings and shared rules. A free account also gets a one-time starter allowance of 10 BYO AI and 5 webQsee AI Standard analyses, so the AI can be tried on a recording of your own before anything is paid for.

Not unless you choose to. Behavior Reports, Event Snapshots, screenshots and videos live inside your browser's IndexedDB until you choose to upload them. When you do enable the Cloud Gallery, there are two modes: in bring-your-own mode uploads go to your own Amazon S3 bucket (or any S3-compatible store like min.io), and webQsee servers physically cannot read them because we don't hold the credentials. In webQsee-provided mode the bucket is one we operate on AWS, in the region you pick at provisioning (Frankfurt, US-Ohio, Tokyo, Sydney, Canada-Central or São Paulo); the payload still moves directly from the browser to S3 via presigned URLs, but it is stored with us. Since webQsee 9.3 its recorded data (events, request and response bodies, cookies, attached files, saved AI analyses) is encrypted in your browser before upload; videos, screenshots and thumbnails are not, so a browser can show them. webQsee keeps the keys so that your team and your link recipients can open an item, which means this is not end-to-end encryption. A temporary link works the same way, with or without an account, on webQsee's temporary storage in the EU. In either mode, webQsee's metadata backend in the EU stores the titles, descriptions, owner and status, plus the item keys encrypted with a key of ours; the actual capture bytes never traverse the backend. The one feature that sends part of a recording to our servers is webQsee AI: a budgeted excerpt, masked by default, which we pass on to a model inside the EU and keep no part of. BYO AI and Deep Inspection never pass through webQsee. You confirm each of these before it happens for the first time; see what the AI analysis sends, and where.

No, and we do not call it that. On webQsee's storage the recorded data of an item is encrypted in your browser before it is uploaded, so a copy taken from the storage alone cannot be read. The keys are kept by webQsee, encrypted with a key of our own, because that is what lets your team and the people you send a link to open the item without exchanging keys. Videos, screenshots and thumbnails are stored unencrypted, so that a browser can show them straight from the storage. If you want nobody but your own team to hold the data, connect your own S3 bucket on Pro or Studio: webQsee never sees its contents, and the same browser-side encryption can be switched on for it in the storage settings. Details are in the privacy policy, section 4.2.

Chrome 103+ and Microsoft Edge 103+, plus most other Chromium-based browsers that support Manifest V3 and the chrome.debugger API. Firefox is not currently supported because webQsee relies on the chrome.debugger protocol, which Firefox doesn't expose to extensions. Safari is not supported either, including for view.webqsee.com.

It's the web mode of webQsee: the same analyzer UI, the same gallery, the same replay and the same exports, running in a normal browser tab instead of behind the extension button. Recipients of a shared capture open it there without installing anything. The one thing web mode cannot do is capture live traffic, because that needs the browser's debugger API, which only an extension gets. So it opens, inspects, replays and exports existing captures; recording them is the extension's job. For the same reason the two Inspected Page exports (MHTML and cookies) are extension-only.

Same way as any other extension: open the browser's extensions page (Chrome: chrome://extensions, Edge: edge://extensions), find webQsee, and click Remove. All locally stored captures and settings are deleted together with the extension.

Two different limits can produce that message. The first is webQsee's own Local Gallery cap: 15 items without an account, 30 with a free account, unlimited on any paid plan. The second is your browser's IndexedDB quota, a per-origin limit set by Chrome / Edge that no extension can raise. In both cases the fix is the same: delete captures you no longer need, or move them into the Cloud Gallery. The gallery shows a live quota meter so you can see where you stand before you hit either one.

Yes, and you do not need a subscription for it. Recording, replay and the analyzer are free and need no account. A free account adds a one-time starter allowance of 10 BYO AI and 5 webQsee AI Standard analyses, which is enough to see what the AI makes of a recording of your own. Beyond that a booster is a one-time purchase from €5.90 rather than a plan to remember to cancel. For a larger rollout that needs more evaluation time, get in touch and tell us your team size and use case.

Chrome and Edge disable extensions in incognito by default. To use webQsee there, open chrome://extensions → webQsee → Details → toggle Allow in incognito. Captures made in incognito are kept like any other: webQsee runs as one extension across your normal and incognito windows, so they land in the same Local Gallery and stay there after the incognito window closes. Delete them in the gallery if they should not.

webQsee's own services, the account metadata, the cloud gallery index, the sharing tokens and the billing records, run inside the European Union. Capture payloads are a separate question and depend on where you put them: in your browser only (the default), in your own S3 bucket (we cannot read it), or in webQsee-provided storage, which lives in whichever of the six AWS regions you picked at setup. That last one is not automatically the EU, so pick Frankfurt if EU residency is a requirement. See the Cloud Storage guide for the full picture.

webQsee runs on Chrome and Edge on Linux exactly as it does on Windows and macOS, same extension, same features. If your browser supports Manifest V3, webQsee works.

Password managers such as Passbolt, LastPass, Bitwarden or 1Password, and a few other extensions like Adobe Acrobat, put small frames of their own into web pages, for example next to a login field. Chrome never lets one extension look into another extension's frames, and it enforces that for the whole tab: the moment such a frame appears, it ends webQsee's analysis, and it will not start one while the frame is there. No extension can turn that off. webQsee removes these frames and the analyzer picks the analysis up again, but whatever happened in between is missing, and a recording loses its events from that moment.

So webQsee names the extension and offers to pause it while webQsee analyzes a tab: switched off when the analysis starts, and back on a minute or two after it ends. You may have to unlock your password manager again afterwards. Chrome asks once whether webQsee may manage your extensions, and General Settings → Extensions that interrupt tab analysis lists what webQsee pauses. You can also do it by hand: switch the extension off in chrome://extensions while you test, or limit the sites it may run on in its Details page.