QA SessionLab — Privacy Policy

Last updated: 14 November 2026

Summary

QA SessionLab works entirely inside your browser. It has no servers, no user accounts, no analytics and no tracking. The developer never receives, sees or stores any of your data.

What the extension handles, locally

• Session data: cookies, localStorage and snapshots of the websites you open inside QA SessionLab sessions, so each session stays logged in separately.
• Bug recordings you start: the steps you take, console errors, failed network requests and screenshots of the tab you record. Password-like fields are masked by default.
• Settings: session names, colours, notes and emulation presets.

All of this is stored with chrome.storage on your device only. It is used only to provide the features you use, and it is deleted when you delete a session or recording, or uninstall the extension.

What is never done

• No data is transmitted to the developer or any third party.
• No data is sold, shared, or used for advertising, profiling or creditworthiness.
• No remote code is loaded or executed.

Data you export

Files you choose to export (bug reports, Playwright storageState, backups) are saved where you choose. A backup with "Include logins" or a storageState file contains login cookies: treat it like a password.

Permissions

The extension needs access to the websites you test in order to isolate their cookies and storage per session. The debugger permission is used only on a tab where you turn on device/network emulation or start a bug recording.

Contact

Questions or concerns: open an issue at github.com/adyfk/qa-sessionlab/issues, or report security problems privately via GitHub security advisories.