Extension: Exploratory Testing Agent Last updated: April 2026
1. Overview
Exploratory Testing Agent is a browser extension that helps you automatically scan and test web pages. This policy explains what data the extension accesses, how it is used, and how it is stored.
2. Data We Collect
The extension only processes the following data, and only when you explicitly enable the relevant features:
OpenAI API Key — entered voluntarily by the user to enable AI Mode. Stored locally in chrome.storage.local on your device only.
Page Screenshots — captured from the active tab solely to send to the OpenAI API when AI Mode is enabled. Screenshots are never stored, logged, or transmitted anywhere other than the OpenAI API endpoint.
Page Content — the extension reads the DOM of the page you are testing in order to scan elements and generate test results. This data stays in your browser and is never transmitted to any server by the extension itself.
Crawl Session State — stored temporarily in sessionStorage to support multi-page crawling across navigations. Cleared when the session ends or you click Clear.
3. Data We Do NOT Collect
We do not collect, transmit, or store any browsing history.
We do not collect personal identification information.
We do not use analytics, telemetry, or crash reporting.
We do not share any data with third parties, except as described in Section 4.
4. Third-Party Services
The extension communicates with the following external services, only when you explicitly trigger the relevant feature:
OpenAI API (OpenAI Privacy Policy) — when AI Mode is enabled, a page screenshot and/or your written test cases are sent to api.openai.com using the API key you provide. This transmission is made directly from the extension's background service worker.
Render backend (exploratory-agent-backend.onrender.com) — when you click "Run in Playwright" or save a recorded test, the generated Playwright step data is sent to a cloud backend hosted on Render. The backend executes the Playwright test and returns pass/fail logs. No personally identifiable information is included in these requests — only the test steps (element selectors, actions, and URLs of the pages you chose to test).
No data is sold, shared with advertisers, or used for any purpose other than executing the test you requested.
5. Data Storage
chrome.storage.local — stores your OpenAI API key, selected model, and UI theme preference. This data never leaves your device.
sessionStorage — stores temporary crawl state for the duration of a test session. Cleared when you close the tab or click Clear.
6. Permissions Explained
Required permissions (granted automatically on install):
activeTab — allows the extension to read and interact with the page you are currently viewing, but only when you click the extension icon.
scripting — allows the extension to inject its agent scripts into the active tab so it can scan and interact with page elements.
storage — allows the extension to save your settings (API key, model, theme) locally on your device.
alarms — used to send a periodic keep-alive ping to the Render backend so it does not spin down between sessions.
Optional permissions (requested at runtime, only when you first click the extension icon):
Host access (<all_urls>) — required to inject the agent panel into the page you are testing. Without this permission the extension cannot scan or interact with any page. You are prompted to grant this permission the first time you click the icon; the prompt can be dismissed and the extension will continue to work for reading the welcome page, but the testing panel will not be available until permission is granted.
Host access (onrender.com) — required for the background service worker to communicate with the Render backend when saving or running Playwright tests.
7. Children's Privacy
This extension is not directed at children under the age of 13 and does not knowingly collect data from children.
8. Changes to This Policy
If this policy changes materially, the updated version will be posted at this URL with a revised "Last updated" date.
9. Contact
If you have questions about this privacy policy, please open an issue on the extension's repository or contact the developer directly via the Chrome Web Store listing.