theautomationguy01/gist:37315f936c337fcb8f516dacdc336d04

## gistfile1.txt
# BugTrace QA Recorder - Privacy Policy

Effective date: 2026-03-02

BugTrace QA Recorder is developed by Arif Shah.

Contact:
- Email: theautomationguy01@gmail.com
- LinkedIn: https://www.linkedin.com/in/arif-shah-3b7938111

## 1. Purpose
BugTrace QA Recorder is a QA/debugging extension that captures user-authorized testing evidence (such as network/API activity, console logs, UI interaction events, optional screen recording, and screenshots) to generate shareable QA reports.

## 2. Data We Process
Depending on how the extension is used, the extension may process:
- Network request/response metadata and payload data
- Console logs and runtime error messages
- UI interaction events (click/input/scroll/navigation timing)
- Optional screen recording/video
- Optional screenshots and annotations
- User-configured settings (filters, output path preferences, integrations)

Some captured data may contain personal or authentication-related information if such data appears in the tested application traffic/content.

## 3. How Data Is Used
Data is used only to:
- Generate QA/debug reports
- Help triage issues and regressions
- Support user-requested integrations (for example Slack/Jira) when explicitly configured

## 4. Data Sharing
By default, data is stored locally on the user’s device via exported files.
Data is sent to third-party services only when the user explicitly configures and uses integrations (for example webhook endpoints).

We do not sell user data.

## 5. Data Retention
Retention is controlled by the user through local files and configured storage locations. Users can delete exported files at any time.

## 6. Security
The extension uses Chrome extension APIs and local storage mechanisms. Users should avoid capturing sensitive production data unless required and should use redaction options where needed.

## 7. User Control
Users can:
- Start/stop capture explicitly
- Choose output and export settings
- Configure redaction and filtering options
- Enable/disable integrations
- Delete generated files and extension settings

## 8. Policy Updates
This policy may be updated over time. The latest version will be made available at this URL.

## 9. Contact
For privacy questions, contact:
theautomationguy01@gmail.com
	# BugTrace QA Recorder - Privacy Policy

	Effective date: 2026-03-02

	BugTrace QA Recorder is developed by Arif Shah.

	Contact:
	- Email: theautomationguy01@gmail.com
	- LinkedIn: https://www.linkedin.com/in/arif-shah-3b7938111

	## 1. Purpose
	BugTrace QA Recorder is a QA/debugging extension that captures user-authorized testing evidence (such as network/API activity, console logs, UI interaction events, optional screen recording, and screenshots) to generate shareable QA reports.

	## 2. Data We Process
	Depending on how the extension is used, the extension may process:
	- Network request/response metadata and payload data
	- Console logs and runtime error messages
	- UI interaction events (click/input/scroll/navigation timing)
	- Optional screen recording/video
	- Optional screenshots and annotations
	- User-configured settings (filters, output path preferences, integrations)

	Some captured data may contain personal or authentication-related information if such data appears in the tested application traffic/content.

	## 3. How Data Is Used
	Data is used only to:
	- Generate QA/debug reports
	- Help triage issues and regressions
	- Support user-requested integrations (for example Slack/Jira) when explicitly configured

	## 4. Data Sharing
	By default, data is stored locally on the user’s device via exported files.
	Data is sent to third-party services only when the user explicitly configures and uses integrations (for example webhook endpoints).

	We do not sell user data.

	## 5. Data Retention
	Retention is controlled by the user through local files and configured storage locations. Users can delete exported files at any time.

	## 6. Security
	The extension uses Chrome extension APIs and local storage mechanisms. Users should avoid capturing sensitive production data unless required and should use redaction options where needed.

	## 7. User Control
	Users can:
	- Start/stop capture explicitly
	- Choose output and export settings
	- Configure redaction and filtering options
	- Enable/disable integrations
	- Delete generated files and extension settings

	## 8. Policy Updates
	This policy may be updated over time. The latest version will be made available at this URL.

	## 9. Contact
	For privacy questions, contact:
	theautomationguy01@gmail.com
No results found