Privacy Policy

Last updated: October 24, 2024

Introduction

Quirx ("we", "our", or "the extension") is a Chrome browser extension that helps users capture screenshots and videos of web pages and create issues across multiple project management platforms (GitLab, Jira, and Trello). This privacy policy explains how we collect, use, and protect your data.

Information We Collect

1. Authentication Credentials

What we collect:

OAuth access tokens and refresh tokens for GitLab, Jira, and Trello
Trello API keys (developer-configured)
Project/workspace identifiers (GitLab project IDs, Jira cloud IDs, Trello board IDs)

How we use it:

To authenticate API requests to your chosen platforms
To create issues, tickets, and cards on your behalf
To upload screenshots and videos as attachments

Storage:

All authentication tokens are stored locally in your browser using Chrome's chrome.storage.local API
Tokens never leave your device except when making authenticated API calls to the respective platforms
OAuth tokens are automatically refreshed when expired

2. Web Page Content

What we collect:

Screenshots of visible web page areas or user-selected regions
Video recordings of tab activity (when you initiate recording)
Current page URL and title
Browser user agent string
Timestamp of capture

How we use it:

To create visual documentation for issues you report
To provide context about where the issue occurred
To attach media to issues on your configured platforms

Storage:

Screenshots and videos are temporarily held in memory during the creation process
Media is uploaded directly to your chosen platform (GitLab, Jira, or Trello)
We do not store media files permanently on our servers (we have no servers)
Media is deleted from browser memory after successful upload

3. Console Logs (During Video Recording Only)

What we collect:

Browser console messages (log, warn, error, info, debug)
Console output from both the web page and extension contexts
Timestamps relative to recording start time

How we use it:

To provide debugging context when reporting issues
To help developers understand what happened during the recorded session

Storage:

Console logs are captured only during active video recording
Logs are included in the issue description when you create an issue
Logs are cleared when you cancel or complete issue creation
We do not store console logs permanently

4. Extension Configuration

What we collect:

Project names you assign to your configurations
Selected provider (which platform you're currently using)
Platform-specific settings (issue types, project keys, etc.)

How we use it:

To remember your project configurations
To route issue creation to the correct platform and project

Storage:

Stored locally in your browser using chrome.storage.local
Never transmitted to any third-party servers
Remains on your device until you delete the extension or clear the configuration

Data Sharing and Transmission

Third-Party Services

We transmit data to the following third-party services only when you explicitly create an issue:

GitLab

(gitlab.com or self-hosted instances)

OAuth tokens for authentication
Screenshots/videos as file uploads
Issue titles, descriptions, and context information

Jira

(Atlassian Cloud)

OAuth tokens for authentication
Screenshots/videos as attachments
Issue titles, descriptions, and context information

Trello

(trello.com)

OAuth tokens for authentication
Screenshots/videos as attachments
Card titles, descriptions, and context information

What We Do NOT Do

We do NOT collect or transmit data to our own servers (we have no servers)

We do NOT sell your data to third parties

We do NOT use your data for advertising purposes

We do NOT track your browsing activity outside of explicit capture actions

We do NOT collect analytics or telemetry

We do NOT share data with anyone except the platforms you explicitly configure

Data Security

Encryption

All API communications use HTTPS/TLS encryption
OAuth tokens transmitted securely using OAuth 2.0 protocols
Screenshots and videos uploaded over encrypted connections

Local Storage

All data stored locally in your browser's secure storage
Chrome's chrome.storage.local provides isolated storage
Data not accessible to other extensions or websites

Access Control

Only you have access to your stored configurations and tokens
Extension only accesses data when you explicitly trigger an action

Permissions Explained

The extension requires the following Chrome permissions:

activeTab

To capture screenshots of the currently active tab

tabs

To read tab URL and title for issue context

scripting

To inject the selection overlay for area-specific screenshots

tabCapture

To record video from the active tab

offscreen

To process video recordings in the background (Manifest V3 requirement)

storage

To save your project configurations and OAuth tokens locally

identity

To handle OAuth 2.0 authentication flows

<all_urls>

To make API requests to GitLab, Jira, and Trello servers

Data Retention

Authentication Tokens: Stored until you delete the project configuration or uninstall the extension
Screenshots/Videos: Held in memory temporarily during issue creation, then deleted after upload
Console Logs: Captured during recording, included in issue, then deleted from local memory
Configuration Data: Stored until you delete it or uninstall the extension

Compliance

This extension complies with:

Chrome Web Store Developer Program Policies
Chrome Web Store User Data Policy
General Data Protection Regulation (GDPR) principles
California Consumer Privacy Act (CCPA) principles

Limited Use Disclosure

Quirx's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Specifically:

We only use Chrome APIs to provide the extension's core functionality (screenshot capture, video recording, issue creation)
We do not transfer user data to third parties except to the platforms you explicitly configure (GitLab, Jira, Trello)
We do not use user data for personalized advertising
We do not allow humans to read user data (all processing is automated)

Consent

By installing and using Quirx, you consent to the collection and use of information as described in this privacy policy.