Privacy Policy — AI Agent Visual Editor

Last updated: 11 October 2026

Summary

What the extension does

AI Agent Visual Editor is a Chrome extension that overlays a visual editing interface on web pages running on your own machine (development servers at localhost or 127.0.0.1). It lets developers select page elements, adjust their visual properties, and send the resulting changes to Claude Code through an MCP server that also runs on their machine.

Data collection

None of its own. The extension collects no personal information, no browsing history and no usage analytics, and it transmits nothing to n'co studio or any third-party service. It does send the changes you make — which include content from the page you are editing — to the MCP server on your own machine, which hands them to your AI coding agent. That path is described in What your agent sees.

Network activity

All network communication stays on your machine:

• The extension opens a WebSocket connection to ws://localhost on a port between 7890 and 7899. That is the @nco-studio/web-editor-mcp server you install and run yourself.
• No data is sent to n'co studio, cloud services, analytics providers, or any other remote endpoint.
• The extension runs only on http://localhost/*, http://127.0.0.1/*, and https://localhost/*. It does not run on public websites.

What your agent sees

The extension sends your data nowhere. Your agent is a separate matter, and worth being deliberate about.

Each change you send carries the following to the MCP server on your machine:

• The page's full address, with every change — including any account id, order number or token in its path or query string.
• The element you edited: its tag, a CSS selector for it, its text, and all of its attributes — so a data-customer-id or a personalised aria-label travels too, even for a purely cosmetic change.
• The before and after values of the properties you changed.
• A second element, in full, when a change needs one — some edits have to touch a parent or sibling to work. It travels with the same detail as the element you edited.
• Any notes you typed, word for word, along with the tag, selector and text of every element you attached them to.
• The source file and line each element maps to, where the dev plugin supplied them, the served path of any image on it, the element's position and size, and an opaque per-tab id.
• Where the property came from — the stylesheet that owns it, the selector, its specificity, and any media query around it. Not only the rule in force: rules for other breakpoints are read and sent too.
• The viewport size and the breakpoint you were working at.
• The element's full inner HTML, but only when you insert, duplicate or paste an element, or make a formatted-text edit. An ordinary spacing or colour change sends no markup.
• Neighbouring and container elements for reorder, insert, group and reparent edits — which can be several elements you did not touch directly.
• A component's name and import path, when you insert one of your project's own components.
• CSS the tool generated for you, such as the rules written by the parallax editor.

Screenshots are the exception: they are stitched and saved in your browser, and never go to the MCP server.

The MCP server runs on your machine, but your agent is the next step, and most agents send what they read to a model provider. Claude Code, for example, is a local program whose model calls go to Anthropic's API — so content you edit reaches Anthropic the same way any file you ask it to read does.

Practically: a development server is not automatically harmless. Local environments are often pointed at a seeded database, a staging copy or a production dump, so the page you are editing may hold real customer records. Treat editing a page the way you would treat pasting that page into a chat with your agent — because in substance that is what it is.

The local MCP server

The extension works with a companion server, @nco-studio/web-editor-mcp, which you run locally with npx. This server:

• Runs entirely on your machine.
• May read your project's configuration files (for example tailwind.config.ts or package.json) to find design tokens and components. Compiling and evaluating them happens entirely on your machine, and the server sends nothing anywhere. What your agent then reads from the server is described below.
• Does not connect to any remote service.

Permissions

Data sharing

This extension shares no data with any third party. It contains no analytics, advertising or tracking, and transmits nothing beyond the localhost connection described above.

The one onward path is the one you create: the MCP server exists to hand your changes to your own AI coding agent, and most agents send what they read to their model provider. That provider is your agent's, chosen by you, under your agreement with them — this extension has no relationship with it and sends it nothing directly.

Children's privacy

This extension is a tool for software developers. It is not directed at children and does not knowingly collect information from anyone, including minors.

Changes to this policy

If this policy changes in a material way, the updated version will be published on this page and the "Last updated" date above will change.

Contact

Questions about this policy: email [email protected] or open an issue at github.com/n-co-studio/web-editor.