This Privacy Policy describes how the QA AI Assistant Chrome Extension ("we", "our", "us", or "the extension") handles and protects user data. We are committed to ensuring your privacy and protecting the security of your test data and credentials. We strictly adhere to a policy of no user tracking, no selling of user data, no advertising, and no analytics.
No Developer Servers, No Tracking, and No Advertising: We do not operate developer-owned servers, run analytics, show ads, or track your behavior. All configurations and captured data remain stored locally in your browser under your absolute control, except when you intentionally and directly communicate with your configured AI providers or Jira via secure HTTPS.
1. Data We Collect
To perform its functions as a QA helper and test-case generation utility, the extension processes and saves the following types of information:
- API Keys & Configuration: API keys for AI models (e.g., OpenAI, Anthropic, Gemini, Groq, DeepSeek, etc.) that you configure.
- Jira Credentials: Your target Jira domain, account email, and Jira API token to allow logging bugs and creating issues directly from the extension.
- Bug Descriptions & Test Cases: Draft bug reports, test scripts, and scenarios entered or selected by you for AI-powered processing.
- Browser Recordings & Assets: Screenshots and video capture recordings generated during your QA testing flow to document bugs.
2. How Data is Stored
We respect the integrity of your local system environment. The extension handles storage according to these principles:
- Local Storage Only: All configurations, API keys, credentials, and recording metadata are saved locally within the user's browser profile.
- Chrome Storage API (Local): We utilize the
chrome.storage.local API to store configurations and credentials, which ensures data is kept on your machine and is not synced to Google's cloud servers.
- Session Storage (Temporary): Temporary recording state and active session parameters are stored using the
chrome.storage.session API. This data is strictly temporary, kept only in memory, and cleared automatically when the browser session ends or the extension is closed.
- No Extension Servers: We do not host or operate any backend servers. No data collected by this extension is ever stored, analyzed, or received by us.
3. Data Transmission
All communication with external services occurs directly from your browser. There are no developer-owned servers, and no analytics or tracking servers are used. Communication occurs only when you explicitly perform an action (e.g., requesting AI analysis or logging a bug). All network communication is conducted securely over HTTPS.
The extension transmits data ONLY to the following user-configured endpoints depending on the services you enable:
- Jira Cloud & Test Management Integration:
https://*.atlassian.net/* (direct communication with your Jira Cloud instance to manage issues)https://tcms.aiojiraapps.com/* (direct communication to manage test cases via Jira-compatible plugins)
- User-Configured AI Service Providers:
- OpenAI (
https://api.openai.com/*)
- Anthropic (
https://api.anthropic.com/*)
- Google Gemini (
https://generativelanguage.googleapis.com/*)
- Groq (
https://api.groq.com/*)
- DeepSeek (
https://api.deepseek.com/*)
- Zhipu GLM (
https://open.bigmodel.cn/*)
- Hugging Face (
https://router.huggingface.co/*)
- OpenRouter (
https://openrouter.ai/*)
- EcomAgent (
https://api.ecomagent.in/*)
These external integrations are entirely configured by the user, and credentials/keys are transmitted directly to the respective endpoints without passing through any third party or developer servers.
4. Required Permissions & Justifications
The extension requests specific browser permissions in manifest.json to perform its testing and automation features. Below are the details and justifications for each key permission:
<all_urls> / Content Scripts
The extension is designed for software testing and may operate on any website selected by the user. Content scripts are injected only when required for QA features, allowing the QA Test Data helper to appear on target websites, inspect inputs, and autofill test data.
tabCapture
Required to record the active browser tab's screen and audio when you initiate a bug capture/recording session.
downloads
Required to download generated bug recordings, screenshots, and export files directly onto your local machine.
scripting
Required to inject the interactive recording toolbar and page-helper styles into web pages you are actively testing.
storage
Required to save your configured API keys, AI model preferences, Jira credentials, and active recording configurations locally.
activeTab
Required to temporarily access the currently active tab when you trigger extension features via the popup or context menu, enabling target style injections and QA data entry helpers without requesting permanent wide access.
tabs
Required to inspect tab details (such as current URL and title) to create context-aware prompts for test-case generation and ensure the extension's QA tools are mapped to the correct tab.
offscreen
Required to spawn offscreen documents for processing and encoding media recordings in the background without interrupting the user experience or blocking main service worker threads.
notifications
Required to show desktop notifications informing you when a test case generation is complete, a bug report is successfully logged to Jira, or when a recording has finished exporting.
5. User Rights & Control
You maintain full ownership and control over your data. You can manage or delete your stored data at any time:
- Clearing Settings: You can clear your API keys or disconnect Jira credentials at any time directly through the extension's Options page.
- Complete Erasure: Uninstalling the QA AI Assistant extension from Chrome immediately and permanently removes all stored data, API keys, and settings from your browser profile.
6. Contact Developer
If you have any questions or feedback regarding this Privacy Policy or the security of the QA AI Assistant Chrome Extension, please contact the developer: