Legal
coTestPilot is developed by Testers.AI. Questions or concerns? Reach us at privacy@testers.ai.
The table below describes every category of data coTestPilot works with:
| Data | Where it's stored | When it leaves your device |
|---|---|---|
| Extension settings (sheet URL, AI model preference, theme, toggles) | Local only chrome.storage.local |
Never |
| Saved test cases (page-level, per-URL) | Local only chrome.storage.local |
Never |
| Bug report drafts | Local only In-memory, cleared on close |
Only when you click "Submit bug" — sent to your configured Google Sheet |
| Page context snapshot (URL, page title, visible text, form fields) | Local only In-memory, not persisted |
Sent to AI API when you trigger an analysis (test generation, page analysis, bug suggestions) |
| Screenshots / annotated images | Local only In-memory during session |
Sent to AI API only when you include them in an analysis prompt |
| Selector / element context (clicked element, attributes) | Local only In-memory, not persisted |
Sent to AI API when you ask coTestPilot to analyze an element |
| Filed bug reports | Optional / external | Sent to your own Google Sheet (configured by you) via a Google Apps Script endpoint you control |
| Crash / error logs | Local only | Never — errors are logged to the browser console only |
When you trigger an analysis (generate test cases, analyze page, suggest bugs, chat, etc.), coTestPilot sends a prompt to an AI API. The prompt includes:
This data is sent to the AI provider configured in your settings (powered by Testers.AI). It is used solely to generate your requested output. Testers.AI's data handling follows their own privacy policy.
coTestPilot never sends passwords, form values, cookies, or authentication tokens to any external service.
If you configure a Google Sheets URL in Settings, bug reports you file are sent to that sheet via the Google Apps Script endpoint you provide. This endpoint is:
If you don't configure a sheet URL, no data is sent anywhere when you file bugs (the submit button will do nothing or show an error).
coTestPilot requests the following Chrome permissions and uses them as described:
| Permission | Why it's needed |
|---|---|
sidePanel |
To show the coTestPilot sidebar without opening a new tab |
scripting |
To inject the content script that reads page context and enables element inspection |
tabs |
To detect page navigation and update the sidebar URL display |
storage |
To save your settings and test cases locally |
activeTab |
To read the currently active tab's URL and title |
Host permission (<all_urls>) |
Required to inject the content script on any page you're testing |
All data stored by coTestPilot lives in your browser's local storage and is fully under your control:
chrome://extensions, click Details on coTestPilot, then "Clear data"Data sent to AI APIs during inference is not stored by us after your response is returned. See Testers.AI's privacy policy for AI provider retention details.
coTestPilot is a professional testing tool intended for adults. We do not knowingly collect information from anyone under 16.
coTestPilot is in beta and evolving quickly. We may update this policy as new features are added. When we make material changes, we'll update the "Last updated" date at the top of this page. Continued use of the extension after changes means you accept the updated policy.
Questions about this policy? Email us at privacy@testers.ai or visit testers.ai.