Quirx Logo
Quirx
How it Works Features Integrations Benefits Feedback
How it Works Features Integrations Benefits Feedback

Cookie Policy

Last updated: October 24, 2024

Introduction

This Cookie Policy explains how Quirx ("we", "our", or "the extension") uses cookies and similar technologies. As a Chrome browser extension focused on privacy and security, we maintain a minimal approach to data collection and storage.

Our Cookie Usage

Good News!

Quirx does not use traditional cookies. As a Chrome extension, we use Chrome's built-in storage APIs instead, which are more secure and privacy-focused than traditional web cookies.

What We Use Instead of Cookies

Instead of cookies, Quirx uses Chrome's chrome.storage.local API to store essential data locally on your device. This is different from cookies in several important ways:

Traditional Cookies

Not Used
  • Sent with every HTTP request
  • Accessible by websites
  • Can be tracked across sites
  • May have security vulnerabilities

Chrome Storage API

What We Use
  • Stays on your device only
  • Not accessible by websites
  • Isolated from other extensions
  • More secure and private

Our Privacy Commitment

No Tracking

We don't use cookies or any other technology to track your browsing activity across websites.

Local Storage Only

All your data stays on your device. We don't have servers to collect or store your information.

Full Control

You can delete all stored data at any time by removing project configurations or uninstalling the extension.

What We Store Locally

While we don't use cookies, we do store the following data locally using Chrome's storage APIs:

Authentication Tokens

Purpose: To authenticate with GitLab, Jira, and Trello

Storage Duration: Until you delete the project or uninstall the extension

Type: OAuth access tokens and refresh tokens

Project Configurations

Purpose: To remember your connected projects and settings

Storage Duration: Until you delete the configuration or uninstall the extension

Type: Project names, IDs, selected platforms

Temporary Session Data

Purpose: To store screenshots and recordings during issue creation

Storage Duration: Deleted immediately after upload or cancellation

Type: Image and video data in memory

Managing Your Stored Data

You have full control over the data stored by Quirx. Here's how you can manage it:

Delete Project Configurations

Open the Quirx extension and navigate to Settings. You can delete individual project configurations, which will remove all associated authentication tokens and settings.

Clear Extension Data

Right-click the Quirx extension icon, select "Manage Extension", then scroll down to "Clear browsing data". This will remove all locally stored data.

Uninstall the Extension

Removing the extension from Chrome will automatically delete all locally stored data, including authentication tokens and project configurations.

Revoke OAuth Access

You can revoke Quirx's access to your GitLab, Jira, or Trello accounts directly from those platforms' settings pages.

Questions?

If you have any questions about our use of cookies or this Cookie Policy, please contact us through the Chrome Web Store listing or visit our Privacy Policy for more information about how we handle your data.

© 2025 Quirx. All rights reserved.

FAQ Privacy Policy Cookie Policy Terms & Conditions