QAgentExtQAgentExt Privacy Policy
QAgentExt is a browser testing extension made by Shubix, developed by Shubham Singh. Core testing and saved test data are processed in your browser. Testing a website can send requests to that website, and some optional features send information to destinations you choose. This policy describes that access, storage and sharing.
Questions about your data: shubix.connect@gmail.com.
Data the extension accesses
To find controls, execute tests and explain results, QAgentExt can read page content, element attributes, accessible names, current URLs, tab information and frame structure. Recording captures interactions and entered values. Audits and diagnostics can inspect console messages, network request and response information, and the rendered page; screenshots may include visible application data.
The extension declares access to <all_urls> and loads content scripts automatically on matching pages and frames. Those scripts may be present before you start a test. Testing, recording and scheduled monitoring use this access to carry out the workflows you configure. Chrome restricts access to certain protected pages.
When you run a flow in the iOS tab, the extension also receives what the Appium server you connect to returns: command results, screenshots of the device screen and the app's element tree.
Test commands, recordings, profiles, session snapshots and diagnostics can contain personal information, credentials or other application data. Password masking in a preview or export does not ensure that every sensitive value has been removed.
What is stored locally
QAgentExt uses Chrome extension local and session storage for its operation. Depending on the features you use, this includes:
- Recorded drafts, saved tests, reusable blocks, suites, imported data and environment profiles.
- Run history, results, diagnostic evidence, screenshots and visual or accessibility baselines.
- Selector memory, element fingerprints and preferences.
- Session snapshots, which may include page storage values and authentication-related data.
- Monitor definitions, schedules, optional webhook URLs and monitor history.
- iOS tab settings (the Appium server address, device, iOS version, app bundle id and UDID you enter), saved iOS flows and a short list of recent iOS run outcomes. Screenshots and element trees from an iOS run are kept in memory for that run and are written to a file only if you download them.
- The text-spacing editor's values and whether they are switched on, so they apply to the next page you open until you switch them off. Applying them adds a stylesheet to the page you are viewing and measures which text then clips or overlaps; nothing is sent anywhere and no page content is stored.
- Temporary execution and inspection state used to reconnect the side panel or recover a run.
Secret values typed into the iOS tab are not stored. They are kept in memory while the side panel is open, and are never written to storage, included in exported plans or run files, or shown in results.
The extension does not use Chrome sync storage to synchronize this data to your Google account. Saved information remains until you delete it, remove the extension or the relevant history retention limits replace older entries. Exported files are stored wherever you save them.
When information leaves the browser
Applications and APIs you test
Navigation, clicks, typing and form submissions can cause the application under test to send its normal requests. Explicit API steps send the URL, headers and body you configure to that endpoint. Requests can use the application's browser session according to browser rules. These actions may change server data, and the destination's privacy policy applies.
Optional monitor webhooks
A monitor sends a webhook only when you configure its URL. The summary includes schedule and folder identifiers, pass/fail/total counts, status and timestamp, plus an accessibility score when available. This summary does not include screenshots or full page content, but identifiers can still reveal information about your test organization. The destination is your chosen service, such as your own server or a messaging webhook provider.
Optional background monitoring opens the configured page in an inactive tab, runs your saved checks and closes that tab when the run finishes. Loading that page and executing its tests can make application requests. Remove the webhook URL to stop summaries, and disable or delete the monitor to stop future scheduled runs.
Appium server for iOS device runs (version 2.2, preview)
The iOS tab drives an iPhone, iPad or simulator through an Appium server that you install and start yourself, normally on the same Mac at http://127.0.0.1:4723, which is the default. QAgentExt does not install, start or include Appium.
Only when you press Check or Run on device, the side panel sends standard WebDriver requests to the server address shown in the iOS tab. They contain the target you entered (device name, iOS version, UDID, app bundle id or Safari) and the flow's commands, such as find this element, tap, type this text or take a screenshot. Text that a flow types, including the value of a secret, is sent so the device can type it.
Nothing is sent to Shubix or any other party. If you enter the address of another machine, that machine's Appium server receives the same requests, so use only servers you control or trust.
Fonts
The extension panel loads font styles and files from fonts.googleapis.com and fonts.gstatic.com. Google receives ordinary network request information, including your IP address and request metadata. Test commands and reports are not included in those font requests. See Google's privacy policy.
Exports, issue links and support
Reports, screenshots, scripts, test libraries and bug packs can contain application data. You decide where to save or share them. Opening a generated GitHub or Jira issue link sends its prefilled URL content to that provider; review it before opening or submitting. Files you email to support are received by the support email provider and Shubix. Send only the information needed to investigate your request.
Core testing requires no QAgentExt account or external AI service. The extension does not automatically upload your test library or run reports to a Shubix backend for processing, and does not include an advertising or analytics service. We do not sell test data or use it for advertising. Support information you choose to send is used to respond to and investigate your request.
Permissions and their purpose
| Permission | Purpose |
|---|---|
sidePanel | Display the primary testing workspace beside the page. |
activeTab | Support page access and capture following a user gesture. |
scripting | Inject testing code, audits and configured page-context tools. |
tabs | Read target tab information and manage test or monitor tabs. |
storage | Store tests, preferences, evidence and execution state. |
webNavigation | Inspect frame structure for routing page actions. |
notifications | Display supported test and monitor completion notices. |
alarms | Schedule monitors configured in the extension. |
<all_urls> | Access authorized test applications on different sites, including matching frames and configured requests, and reach the Appium server address you enter for iOS runs. |
Site access is broad and is not limited to clicking Record. You can review or restrict site access in Chrome's extension settings; testing or monitoring on restricted sites may then stop working.
Your controls and deletion
- Use the library and profile controls to remove saved items, and the Dashboard storage controls to clear the categories they expose.
- Delete saved iOS flows in the iOS tab. Closing the side panel discards any secrets typed there.
- Disable or delete scheduled monitors before clearing their stored data. Remove a monitor's webhook URL to stop future summaries.
- Removing QAgentExt from Chrome removes its extension storage. Downloaded files, data in the tested application and information already shared with another service are managed separately.
- Stopping a run cannot undo a request or action already received by your application or device.
- Contact shubix.connect@gmail.com about information you previously sent to support.
This website
This site serves its own images, video, captions and styles. Playing the demo requests the video from the site host, and downloading the companion CLI package from /cli/ is an ordinary download from the same host. The site adds no analytics scripts or embedded third-party video player. The hosting provider, Netlify, receives ordinary web requests and may process connection and access-log information under its privacy policy. Following a Chrome Web Store, social, email or other external link is subject to that destination's practices.
Until October 2026 this policy was published at shubix.netlify.app/qagentext/privacy/; that address now leads here.
Policy updates
We will update this page and its date when the described data handling changes. The Chrome Web Store listing identifies the extension version available to install.