Privacy Policy for Signal
Last updated: January 2026
Your privacy is important to us. This Privacy Policy explains how the Signal Chrome Extension collects, uses, and protects your data.
1. Data Collection & Purpose
Signal is a developer tool designed to assist in debugging and reporting web application issues. To fulfill this purpose, the extension temporarily captures the following data while you explicitly enable "Recording":
- Page Content: Screenshots and video recordings (screencasts) of the tab being debugged.
- Technical Logs: Console logs, error messages, and stack traces generated by the website.
- Network Activity: HTTP/HTTPS requests and responses (HAR data), including headers and payload bodies.
- User Interactions: Clicks, mouse movements, scrolling, and keyboard inputs (excluding password fields).
This data is collected solely for the purpose of generating an "Investigation Report" for your own use.
2. Data Storage
All data is stored locally on your device within your browser's memory and local storage. Signal does not have a backend server, database, or cloud storage. We do not transmit your data to us or any third parties automatically.
3. Data Sharing
You are in full control of your data. Data is only shared when you explicitly choose to:
- Download Report: Generates a JSON file on your computer.
- Create JIRA Ticket: If you configure the JIRA integration, the extension will send the report data directly to your connected JIRA instance/API. This transmission happens directly from your browser to Atlassian's servers, authenticated by you.
4. Sensitive Information & Redaction
We implement safety measures to minimize the risk of capturing sensitive data:
- Password Fields: Input into fields with
type="password"is masked (recorded as***). - Authorization Headers: We automatically redact standard
Authorization: Bearertokens in the recorded network logs.
As Signal records the visible screen and general network traffic, please exercise caution and pause recording when navigating pages displaying sensitive personal or financial information not intended for the debug report.
5. Permissions
The extension requires the following permissions to function:
debugger- To attach to the tab and capture console/network/screencast data.tabs&activeTab- To identify which page to record.storage- To save settings and the temporary report data locally.scripting- To inject the recording widget and edit tools into the page.
6. Changes to this Policy
We may update this privacy policy from time to time. If we make significant changes, we will notify users through the extension updates or listing page.
7. Contact
If you have questions about this policy, please contact us via the Chrome Web Store support page.