Your data stays on your computer.

QA Scout has no server, no account and sends no data. This page explains what the extension records, where it stores it and what it never does.

What the extension records

Only during a test session in progress and only in the tabs you choose to follow (including same-site iframes; iframes from other sites, such as ads, are left out). In the test browser opened by the qa-scout command, every tab of that separate browser:

• Clicks: the type and name of the clicked element (for example, “button Pay by card”), with a screenshot of the visible tab.
• Filled fields: only the field label. The typed value is never read or stored. In password fields, the note only says “Filled in a password field”. For attachments, only that a file was chosen, never its name or content.
• Option lists (select): the text of the chosen option, which comes from the page itself (for example, “Chose CA in State”). Lists marked as card, birth date or password data (autocomplete) only record that an option was chosen.
• Opened pages: title and address. Usernames, passwords, tokens and codes in the address are replaced with *** before saving.
• JavaScript errors, console.error and network failures: the error message, method, request path and response code. Request and response bodies are not read.
• Alt+Shift+M and Alt+1 to Alt+5 shortcuts: a screenshot of the visible tab at that moment, with the note type when it is Alt+number.

With the session paused or finished, nothing is recorded.

Exploring with Claude (MCP server, optional)

Anyone who installs the QA Scout MCP server in Claude Code or Claude Desktop can ask Claude to run a session in the test browser. In this mode, the session, notes and screenshots still stay only on your computer, but Claude needs to read the screen to explore: the text and fields of visited pages (including values already filled in) are sent to Claude, as in any conversation with it. Use only test environments and test data. The Chrome Web Store extension does not use this mode.

Where the data lives

Sessions, notes and screenshots stay in the browser's local storage (chrome.storage.local in the extension, localStorage on the web version). Nothing is sent to QA Scout or third-party servers. Data only leaves your computer when you copy a report, copy a bug or download a backup.

A word about screenshots

Screenshots show what is on screen at the moment of the click. If you explore a system with real customer data, it may appear in the images. Prefer test environments with fake data and review the screenshots before sharing a report.

Why the extension asks for each permission

• Site access (<all_urls>), optional: not requested at install. Chrome asks the first time you click “Follow the current tab”, because the system under test can be at any address and the tab screenshot requires this access. You can revoke it any time in chrome://extensions. Even with access granted, the capture only runs in followed tabs while a session is in progress.
• tabs and scripting: know which tab you marked, take its screenshot and record clicks and fields.
• webRequest: notice error responses (4xx and 5xx) and connection failures in followed tabs. Read only; no request is blocked or changed.
• storage and unlimitedStorage: keep sessions and screenshots on your computer.
• sidePanel: open QA Scout in Chrome's side panel.

How to delete everything

Uninstall the extension or clear its data in chrome://extensions. In the test browser, delete the ~/.qa-scout/perfil folder. On the web version, clear the site data in your browser.

Open source

QA Scout's code is open (MIT license): you can check everything it does. Privacy questions: contato.qascout@gmail.com.

Changes to this policy

If QA Scout ever sends any data off your computer (for example, in a future optional sync), this page will be updated first, and the feature will only be turned on with your consent.