Privacy Policy

Data the extension accesses

To do its job, the extension accesses:

• The content of the page you are actively working with. While you are recording or replaying a flow, the extension uses Chrome's debugging protocol (the debugger permission) and a content script to read page structure (DOM/accessibility tree), take screenshots, and interact with elements (click, fill, navigate), only on the tab you have targeted, only while you are actively using the extension against it. It is never active in the background across your other tabs or browsing.
• Your project files. Flows, page objects, scenarios, and variables are read from and written to a folder on your own computer that you explicitly choose via Chrome's File System Access API ("Connect folder"). The extension never accesses any other folder on your disk.
• One local UI preference (which SQL dialect to use for generated assertions), stored via chrome.storage.local. This never leaves your browser.

Data the extension does not collect

• No analytics or telemetry of any kind.
• No browsing history or activity outside the tabs you are actively recording or replaying against.
• No account, profile, or personally identifying information.
• No data is ever sent to the developer or to any server the developer operates. None exists.

How data is shared

It is not. The extension has no backend server. The only network communication it ever makes is a WebSocket connection to ws://127.0.0.1:<port>, a local bridge that lets an AI coding agent (for example Claude Code, running the accompanying MCP server) on the same machine inspect and drive the flow you are building, if and only if you have started that agent yourself and approved its connection in the side panel. This traffic never leaves your device.

Your project data is never used for advertising, never sold, never shared with third parties, and never used to make credit or employment decisions.

Data storage and retention

• Project data (flows, page objects, scenarios, variables) lives as plain files in the folder you chose, under your full control. Edit or delete them anytime, the same as any other file on your computer.
• The one stored UI preference is cleared automatically if you remove the extension.

Why the extension requests its permissions

• debugger: drives the tab you are actively recording or replaying against (clicking, filling, navigating, inspecting) via Chrome's debugging protocol. Not used to monitor any other activity.
• activeTab / tabs: lets you pick which open tab a flow targets.
• scripting: injects the element picker into the page you are working with.
• <all_urls> (host permission): the pages you want to build tests against can be any site, so the picker and replay engine need to be able to run on any of them. It only actually runs on tabs you target.
• sidePanel: hosts the extension's UI.
• storage: the one local UI preference described above.

Children's privacy

The extension is a developer tool and is not directed at children.

Changes to this policy

If what the extension collects or how it is used ever changes, this policy will be updated and the change called out in the extension's release notes before the update is published.

Contact

Questions about this policy: vitalii.yanchuk.v@gmail.com