Last updated: April 9, 2026. This policy explains how we handle markdown content, device-level signals, and third-party scripts when you use MarkdownToWord.art.
If you do not agree with this policy, please stop using this site.
These points reflect current product behavior for Markdown, DOCX, HTML, PDF, and Google Docs export flows.
When you choose Word or DOCX, your markdown content is sent to /api/markdown-to-word for conversion and file response.
These flows are handled in your browser environment, reducing server-side content processing for those output paths.
Cloudflare Turnstile verification is used before Word or DOCX conversion requests are accepted.
This site does not provide account-level saved project history as a product feature.
The site may store locale or display preferences in browser storage for better UX.
In production or debug mode, analytics, ads, or affiliate providers may be enabled through environment configuration.
Practical privacy details for this converter, written to match how the project currently operates.
We process the markdown content you paste or upload, selected output format, and basic request metadata needed to deliver conversion and prevent abuse.
Markdown is sent to the server when you export as Word or DOCX. HTML export, PDF print flow, and Google Docs copy mode are handled primarily in-browser.
The conversion flow is designed for transient processing and response delivery, and API responses are served with no-store cache headers. Infrastructure logs may still contain limited technical records for security and reliability.
If your markdown references remote images, the server may fetch allowed public image URLs during conversion so images can be embedded in DOCX output. Private or blocked sources may fail to embed.
We use Cloudflare Turnstile to reduce automated abuse and protect conversion capacity for normal users.
We may use browser storage for locale or UI preferences. Third-party analytics, ads, or affiliate tools may also use cookies or similar identifiers based on your browser and region.
Depending on deployment configuration, third parties may include Cloudflare Turnstile, Google Analytics, Microsoft Clarity, Plausible, Vercel Analytics, Google AdSense, PromoteKit, and Affonso.
We do not sell your markdown document content as a product feature. Third-party vendors may process device or event data under their own policies when their scripts are enabled.
This service is not directed to children under 13. If you believe a child submitted personal data, contact us through the site owner's published channel.
Yes. We may update this policy when product behavior, legal requirements, or third-party integrations change. The latest version and date on this page control.
For sensitive or regulated content, avoid pasting confidential data unless your own compliance review approves this workflow.
Actions you can take to control data use when working with MarkdownToWord.art.
You can clear local storage, site data, and cookies from your browser settings at any time.
Do not submit passwords, secrets, or regulated personal data unless you have reviewed legal and security requirements for this workflow.
You can use browser privacy tools, tracking-protection features, or consent controls made available by your environment and region.
Use the contact channel published by the site owner to ask questions about this policy or project data handling.