Use Privacy Mode
For PRO browser conversions, Privacy Mode prevents the Markdown from being stored in cloud history and disables AI summaries for that conversion.
Data-flow disclosure
Local, cloud, API, and MCP are different paths
“Web2MD processes locally” is true for the PRO/TEAM browser conversion engine and local Agent Bridge, but it is not a blanket description of every product path. This page states where content goes, what is stored, and what choice changes the behavior.
| Path | Where conversion runs | What crosses the boundary | Storage and control |
|---|---|---|---|
| PRO/TEAM extension conversion | Your Chrome browser | Rendered 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. |
| Anonymous or FREE extension conversion | Web2MD conversion API | Rendered 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 Library | Web2MD database | Converted Markdown, URL, title, token/word counts, optional summary and tags. | User-controlled storage for search and reuse; entries can be deleted. |
| REST API / hosted MCP | Web2MD servers | Submitted 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 Bridge | Your Chrome + local native bridge | Page 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 AI | Chosen AI provider | Only 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 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 as cloud processing
REST API and hosted MCP are server-side services. Use them for content you are allowed to send to Web2MD.
The short version
Choose the extension or Agent Bridge when browser context matters. Choose Privacy Mode when you do not want a PRO conversion stored in Library. Choose REST API or hosted MCP when server-side automation is acceptable. 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.