Privacy Policy
Short version: e2etest.dev is a local-first Chrome extension. We do not collect, transmit, store on our servers, share, or sell any of your data. Everything you create — scenarios, run results, screenshots, videos, captured network traffic — stays in your browser. We do not have a backend. We do not have user accounts. We do not have analytics.
1. Who we are
"e2etest.dev" (the "Extension", "Service") is a Chrome browser extension operated by e2etest.dev ("we", "us", "our"). This policy explains how the Extension handles information when you install and use it.
For any privacy-related question, contact us at privacy@e2etest.dev or via our contact page.
2. Scope
This policy applies to:
- The e2etest.dev Chrome extension distributed via the Chrome Web Store
- The marketing website at
e2etest.dev
3. What data the Extension processes
The Extension processes — entirely within your browser — the following categories of data while you are actively using it:
3.1 Scenario data
Test scenarios you create (names, steps, selectors, variables, descriptions). Stored locally in your browser's IndexedDB.
3.2 Run results
For each scenario run: step-level pass/fail status, durations, screenshots of the test page, optional video recordings, and metadata of network requests issued by the page being tested (URL, HTTP method, status code, headers, request body, response body — up to 64KB per request). Stored locally in IndexedDB.
3.3 Captured page content
When you pick an element, run a test step, or activate the network interceptor, the Extension reads relevant parts of the page being tested (DOM elements, attributes, text content, request/response bodies). This data is used to execute the test, recorded into your local run results, and never transmitted to us.
3.4 User preferences
Your language preference (Turkish/English) and favorited scenarios are stored via chrome.storage.local.
4. What data we (e2etest.dev) collect
None.
The Extension does not send any of the data above to us, to a third party, or to any remote server we control. We have no server-side database of users, scenarios, or analytics events. We do not deploy tracking pixels, fingerprinting libraries, A/B testing tools, error-reporting SDKs, or any other telemetry inside the Extension.
5. Permissions and why they are required
The Extension requests the following Chrome permissions. Each is used only for the purpose described and never to collect data on you.
| Permission | Purpose |
|---|---|
sidePanel | Host the Extension's user interface in Chrome's side panel. |
storage | Persist your language preference and UI state locally. |
tabs | Read the active tab URL, open new tabs and switch between them as part of multi-tab test scenarios. |
activeTab | Inject the test runner and element picker into the tab you are actively testing. |
scripting | Programmatically inject the runner, selector picker and network interceptor scripts during a scenario run. |
webRequest | Observe network request metadata (URL, method, status, timing) of the page being tested, for inclusion in your local HTML report. |
debugger | Dispatch real OS-level mouse events for the "Hover" test step (synthetic JavaScript events cannot trigger CSS :hover). Attached only during a scenario run; detached immediately after. |
tabCapture | Record the test tab as video when you explicitly enable the "Record run as video" toggle. |
desktopCapture | Open Chrome's native source picker so you can choose which tab to record. We never auto-record anything outside your active selection. |
offscreen | Host the MediaRecorder API in an offscreen document (required by Manifest V3 since service workers have no DOM). |
host_permissions: <all_urls> | Allow you to run tests against any website. The Extension does not access any page unless you have started a scenario or picker action against it. |
6. Where your data is stored
Exclusively on your own machine, inside Chrome's local storage facilities:
- IndexedDB — scenarios, run results, screenshots, video recordings, captured network bodies, crawler results.
chrome.storage.local— small preferences such as your language choice.
This storage is governed entirely by Chrome and your operating system. e2etest.dev has no access to it.
7. Data we do not collect or use
- We do not collect or process personal data (names, emails, IP addresses, device identifiers).
- We do not use analytics tools.
- We do not use third-party tracking or advertising.
- We do not sell or share any data with any third party.
- We do not use the data we process for any purpose other than the one for which it was provided (i.e. executing the test scenarios you build).
- We do not use the data we process for creditworthiness or any related purpose.
- We do not transfer or sell the data we process to third-party data brokers.
8. Third-party services
The Extension does not embed third-party SDKs, analytics, advertising or tracking. The marketing website (e2etest.dev) is hosted on a static-page provider (Cloudflare Pages); the provider may collect basic anonymous request logs (IP, user agent, requested URL) for operational and security purposes. We do not place cookies on the marketing site.
If you choose to use the optional Cowork (Claude in Chrome) integration to author scenarios using AI, that integration runs entirely between Cowork and your browser; e2etest.dev is not involved in or aware of those interactions.
9. AI / large language model use
The Extension itself does not call any AI or LLM service. The AI authoring flow works as follows:
- You click "Cowork auto" inside the Extension.
- The Extension generates a text prompt locally.
- You manually copy that prompt into Cowork (Claude in Chrome), a separate product operated by Anthropic.
- Cowork interacts with the page you are testing, using the in-page
window.sansE2E.authorAPI to record scenario steps directly into the Extension's local storage.
e2etest.dev does not send any data to Anthropic and does not receive any data from Anthropic. Your usage of Cowork is governed by Anthropic's own terms and privacy policy.
10. Children's privacy
The Extension is not designed for or directed at children under 13. We do not knowingly process data of children.
11. Security
Because no data leaves your browser, the security of your stored data depends primarily on the security of your own machine and Chrome profile. We follow industry standard practices in the Extension's code: the Extension's bundle is sandboxed by Chrome, does not load remote code, uses strict content security boundaries between the Extension's privileged context and the pages being tested, and never reads or writes to disk outside Chrome's managed storage.
12. Your rights
Because we do not hold any of your data, conventional data subject requests (access, deletion, portability) are answered directly by Chrome's storage system:
- Export — every scenario can be downloaded as JSON from inside the Extension.
- Delete — delete individual scenarios in the UI, or uninstall the Extension to remove all local data.
- Access — all data is visible in the Extension's UI; Chrome's DevTools also let you inspect IndexedDB directly.
If you have any question or wish to raise a complaint, contact us at privacy@e2etest.dev.
13. Changes to this policy
We may update this policy as the Extension evolves (for example, if future versions add cloud-sync features). Material changes will be reflected by updating the "Last updated" date above and, where appropriate, by surfacing a notice in the Extension itself. Continued use of the Extension after such changes constitutes acceptance.
14. Governing law
This policy is governed by the laws of the Republic of Türkiye. Disputes arising from the Extension or this policy are subject to the exclusive jurisdiction of Istanbul Central (Çağlayan) Courts and Enforcement Offices.
15. Contact
e2etest.dev
Email: privacy@e2etest.dev
Web: e2etest.dev
Contact form: e2etest.dev/contact