Data privacy & security

EDITED MCP is a read-only connection to EDITED's market data. Your AI client requests data — pricing for a set of products, say — and EDITED sends its market data back. A request goes in; a response comes back, as with an API. What the connection doesn't do: read your prompts, your files, or your conversation, or reach into your own systems. The only thing that reaches EDITED is the request your client makes — nothing else of yours.

What this page is about

This page is about EDITED's MCP connection specifically — not a general take on AI tool safety. Two things sit with you, not EDITED: what your organization allows into any AI tool, and what your AI client (Claude, Copilot, ChatGPT, and the like) does with data once it's there. Those are governed by your own policies and your agreement with that provider.

Telling the two apart is the quickest way to scope a review. Much of what can feel like "AI risk" turns out to be within your control. The questions about the connection itself — what it can reach, what data flows, who can see it — are answered here and by EDITED's security review. The questions about what your AI tool does with your data — whether it trains on it, keeps it, or shares it — sit with your own policy and provider agreement. By the end of this page, you should be able to say plainly where EDITED's connection ends and your own controls begin.

Can EDITED see my conversations, prompts, or internal systems?

No.

When you use an AI client, it's the client — not EDITED — that turns your words into a specific request, or "tool call." Your prompt stays between you and your client; only that request crosses to EDITED. (How clients build tool calls is covered in What is MCP.)

So the MCP server only ever responds to an explicit tool call — a request for pricing data, say. It has no mechanism to read the surrounding conversation, your client's other tool calls, or any other content your AI client holds.

EDITED MCP is a source your client calls — it doesn't reach back into your systems. It can't connect to your data warehouse, your store platform, or your internal tools; any wiring between EDITED's data and your own systems happens in your client, on your side. EDITED sees only the parameters passed to the tool that was called — nothing else.

What data actually flows through the connector?

EDITED's own market data — never yours.

What moves through the connector is EDITED's data: scraped, captured, or authored by EDITED, flowing out to the caller. There is no customer data in the system to begin with — a simpler situation than most data-privacy questions assume.

It spans three domains — Competitive Market Data, Trend & Research, and Messaging & Promotions. The data has the full breakdown.

Every tool available today is read-only: there's no write path on the MCP surface, so nothing a caller sends can change EDITED's data or reach anything beyond the tool it called. (See What is MCP for how tools work.)

What about deeper questions — credentials, logging, access controls, certifications?

We can answer those.

How credentials are handled, what's logged, who has access, which certifications apply — we can walk you through all of it. For many teams that's a straightforward conversation; where a full formal security review is the right step, we'll do that too — in detail, and under NDA.

If you're already working with EDITED, your account manager or sales representative can start that process with you. If you're not sure who your contact is, or how to get started, our support team (support@edited.com) can point you to the right person.

This page describes the market-data MCP connection only. If you use other EDITED products or services, those may involve different data and terms — your account manager can clarify.

For the mechanics of how a key is issued, sent, and managed, see Authentication & access.

In short

EDITED MCP sends its own market data out to you, read-only. It can't see your prompts, your files, or your systems — only the request your client makes. Anything beyond that structural picture — the operational detail a security team works through — we're happy to walk through with you. Not sure who to ask? Email support@edited.com.