Data-flow disclosure

Local, cloud, API, and MCP are different paths

“Web2MD processes locally” is true for ordinary PRO/TEAM webpage conversion and local Agent Bridge, but it is not a blanket description of every product path. PDF and Office-file extraction is server-side. This page states where content goes, what is stored, and what choice changes the behavior.

PathWhere conversion runsWhat crosses the boundaryStorage and control
PRO/TEAM webpage conversionYour Chrome browserRendered page HTML stays in the browser for conversion.The result is saved to cloud Library by default; turn on Privacy Mode to skip content storage.
PDF / Office file to MarkdownWeb2MD conversion serviceThe file bytes are sent over HTTPS for server-side parsing, including files selected locally or read from a browser tab.Raw uploads are processed in memory rather than saved as source files. The Markdown result follows the applicable account and Library settings.
Anonymous or FREE extension conversionWeb2MD conversion APIRendered HTML is sent over HTTPS because quota enforcement and conversion run server-side.Anonymous results are not attached to an account. Signed-in FREE history may store the result unless Privacy Mode is on.
Cloud LibraryWeb2MD databaseConverted Markdown, URL, title, token/word counts, optional summary and tags.User-controlled storage for search and reuse; entries can be deleted.
REST API / hosted MCPWeb2MD serversSubmitted URL or HTML is fetched/processed server-side; output and metadata are returned.Designed for automation. Do not send material your organization does not permit a hosted service to process.
Local Agent BridgeYour Chrome + local native bridgePage access and conversion use the browser session on your computer.Chrome must be running. Authentication is never bypassed. Cloud-history saving follows the extension setting.
Send to AIChosen AI providerOnly happens after the user chooses a provider and sends or pastes the converted Markdown.The selected AI provider then applies its own privacy and retention terms.

Use Privacy Mode

For supported PRO browser conversions, Privacy Mode prevents the Markdown from being stored in cloud history and disables AI summaries for that conversion.

Use Agent Bridge for browser-only sources

The bridge uses the signed-in Chrome session you control. It cannot bypass login, MFA, CAPTCHA, or access rights.

Treat hosted automation and files as cloud processing

PDF and Office files, REST API, and hosted MCP use Web2MD servers. Use them only for content you are allowed to send to a hosted service.

The short version

Choose the extension or Agent Bridge when browser context matters. Choose Privacy Mode when you do not want a supported PRO webpage conversion stored in Library. Treat PDF and Office-file conversion, REST API, and hosted MCP as server-side processing. Sending output to ChatGPT, Claude, Gemini, or another AI is a separate user action governed by that provider.

For legal details and retention terms, read the Privacy Policy.