Last updated: August 11, 2026
TraceSnap QA ("TraceSnap", "we", "our") is a Chrome extension designed to help software testers and developers capture, organize and export evidence from user-initiated browser testing sessions.
TraceSnap is designed with a local-first approach. QA evidence is processed and stored locally in the user's browser and is not transmitted to TraceSnap or to a TraceSnap-controlled server.
Depending on the features you choose to use, TraceSnap may process the following information:
During an active testing session, TraceSnap may process:
The URL of the page being tested
Page title
Time of capture
Information required to associate captured evidence with the relevant browser page
This information is used only to create and organize the QA evidence requested by the user.
TraceSnap can capture screenshots of the active browser tab when the user explicitly requests a capture.
Screenshots may contain any information visible on the tested webpage at the moment of capture.
TraceSnap does not transmit screenshots to the TraceSnap developer.
During an active testing session, TraceSnap may record labeled user interactions in order to generate automatic Steps to Reproduce.
Examples include:
Clicking a button
Clicking a link
Selecting an option
Submitting a form
Other labeled page interactions relevant to reproducing a bug
TraceSnap is designed not to intentionally record the values typed into form fields.
TraceSnap Pro can locally capture console diagnostics produced by the page being tested, including:
Console logs
Informational messages
Warnings
Errors
JavaScript errors
Unhandled promise rejections
Console capture is used only to help the user diagnose and document software issues.
TraceSnap Pro includes an optional Network Capture feature.
Network Capture is disabled by default and is enabled only after the user explicitly activates it and grants the additional browser permission requested by Chrome.
When enabled, TraceSnap may record diagnostic network metadata including:
Request URL
HTTP method
Resource type
HTTP status code
Request timing
Cache information
Redirect information
Network failures
TraceSnap does not intentionally capture or store:
Request bodies
Response bodies
Cookies
Authorization headers
Passwords
TraceSnap also attempts to redact common sensitive URL parameters such as tokens, passwords, API keys, session identifiers and similar values before storing URLs.
Because websites can use arbitrary parameter names, automatic redaction cannot guarantee detection of every possible sensitive value. Users should review exported evidence before sharing it with third parties.
TraceSnap Pro is sold through Gumroad.
When a user activates TraceSnap Pro, TraceSnap sends the following information to Gumroad's license verification service:
The TraceSnap product identifier
The user's Gumroad license key
This communication is used only to verify whether the user has a valid TraceSnap Pro license.
Gumroad's license verification service may return purchase-related metadata. TraceSnap uses only the information necessary to verify the license and determine whether the relevant purchase has been refunded, disputed or otherwise invalidated.
TraceSnap does not intentionally store payment card information or other payment credentials.
No QA screenshots, browsing evidence, console diagnostics, automatic steps or network diagnostics are sent to Gumroad.
Purchases made through Gumroad are also subject to Gumroad's own privacy practices and terms.
TraceSnap uses Chrome's local extension storage to maintain information required for the extension to function, which may include:
Privacy consent
Extension preferences
Active testing session state
Captured QA evidence
TraceSnap Pro license state
TraceSnap does not use this storage to track users across websites for advertising or profiling purposes.
Users can remove session evidence by discarding their testing session and can remove locally stored extension data by uninstalling TraceSnap or clearing the extension's stored data.
TraceSnap does not sell user data.
TraceSnap does not use QA evidence for advertising, profiling, creditworthiness, lending decisions or purposes unrelated to the extension's QA evidence-capture functionality.
QA evidence is not transferred to the TraceSnap developer or to third parties.
The only external data transmission performed by TraceSnap is the information necessary to verify an optional TraceSnap Pro license with Gumroad, as described above.
Any evidence file exported by the user is created at the user's request. TraceSnap does not control what the user subsequently chooses to do with exported files.
TraceSnap does not currently include:
Third-party advertising
Advertising trackers
Behavioral analytics
Cross-site tracking
Developer-controlled telemetry of QA sessions
TraceSnap requests Chrome permissions only when needed to provide its QA evidence-capture functionality.
These may include permissions used to:
Access the active tab selected by the user
Capture the visible tab
Inject packaged scripts required for automatic reproduction steps and diagnostics
Store local session information and preferences
Capture network metadata when the user explicitly enables Network Capture
Optional website and network access is requested only when required for features initiated by the user.
TraceSnap QA evidence is stored locally for as long as required for the active testing session or until the user removes it.
Exported evidence is saved to a location chosen or controlled by the user.
TraceSnap Pro license state may remain stored locally so that users do not need to reactivate their license every time they open the extension.
TraceSnap does not maintain a developer-controlled database containing users' QA session evidence.
TraceSnap is designed to minimize unnecessary transmission of testing data by processing QA evidence locally.
However, screenshots, URLs, console messages and network metadata can potentially contain sensitive information originating from the websites being tested.
Users should avoid capturing confidential information unnecessarily and should review evidence before sharing exported reports or ZIP files.
This Privacy Policy may be updated if TraceSnap's functionality, data handling practices or legal requirements change.
Any updated version will be published on this page with a revised "Last updated" date.
For privacy questions or questions about TraceSnap QA, contact:
admin@glasskai.com
Website: www.glasskai.com