1. The short version

• Free conversions run in your browser. The document you convert is not sent to us.
• We collect an email address only if you create an account, and we use it to sign you in and to know which plan you bought.
• On the website and in the web app we record anonymous usage events (for example "PDF downloaded from the markdown-to-pdf page") that contain no document content. The browser extension records none.
• Batch conversion, merging files into one document, files over 5 MB, a server-rendered PDF you explicitly ask for, and the API upload content to our servers. It is processed in memory and deleted within 24 hours.
• We do not sell data, do not show advertising and do not use your documents to train anything.

2. What we collect

2.1 Account data

When you sign in with an email link or with Google, we store your email address, the identifier returned by the sign-in provider, the time of sign-in and an account ID we generate. We do not store a password because we do not use passwords. This data exists only for people who create an account; the free converter works without one.

2.2 Entitlement and billing data

When you buy a plan we store which plan it is (7-Day Pass, Pro monthly, Pro yearly, Lifetime), its start and end dates, its status, the customer and subscription identifiers assigned by our payment provider, and the number of devices signed in. We never see or store your card number; payment details are entered on our payment provider's page and held by them.

2.3 Website and web app analytics

When configured, optional Google Analytics 4 and Baidu Analytics help us measure page visits and converter actions. They are loaded only after you choose Accept analytics. You can decline or change your choice through Analytics preferences. They are not loaded when your browser sends Global Privacy Control or Do Not Track. We send page paths and event names, and may send the output format or feature name; we do not send your document text, file name, email address, URL query parameters or URL fragments in these events. Authentication callback pages are excluded.

These providers receive standard network information, including IP address and browser information, and may set analytics cookies after consent. Separately, when our account backend is configured, we may store basic converter events with a random browser identifier and no document content. Global Privacy Control, Do Not Track and a declined analytics choice also stop these events.

The browser extension is different and is not covered by this section. The extension does not record or send usage events of any kind, and there is consequently no analytics setting in its popup. What it does send is listed in section 6.

2.4 Error reports

If a conversion fails, we record the error message, the stack trace, the browser version and which conversion options were on. We strip document content from error reports before they are sent; if a message would contain part of your text, only its length is kept.

2.5 Server logs

Our web servers keep standard access logs (requested URL, time, status code, user agent, IP address) for 30 days for security and capacity planning, after which they are deleted. IP addresses are not joined to account data.

2.6 Support email

If you write to us, we keep the email thread, including any Markdown you attach to reproduce a problem, for as long as needed to resolve it and for up to 12 months afterwards.

3. What we do not collect

• The documents you convert for free. Parsing and file generation happen inside your browser tab or inside the extension. No part of the text, images or file is transmitted to MDtoDOCX. You can verify this in your browser's network inspector.
• Your browsing history. The extension's content script runs only on the AI chat sites listed in section 6 and reads a page only when you click Export or use the right-click menu on selected text.
• Contents of other tabs, keystrokes, clipboard contents (other than what you explicitly copy with the Copy as rich text button), or files on your computer other than the one you drop into the converter.
• Precise location, device identifiers, contacts, or data from other extensions.
• Payment card numbers. These are handled entirely by our payment provider.

4. When a document does leave your device

Four situations send content to our servers, and each one is labelled as such in the interface, with the exact sentence describing the upload, before anything is sent:

• Batch conversion (Pro): converting more than one file at once.
• Merging into one document (Pro): combining several files into a single .docx or PDF.
• A source file larger than 5 MB, or a server-rendered PDF you explicitly asked for (Pro): there is no page-count rule; the trigger is the file size or your own choice of the server route. Every PDF requested from the browser extension also goes this way.
• The MDtoDOCX API: conversions requested programmatically with an API key.

For these, the content is sent over TLS, processed in memory on our rendering servers, and the output is returned to you. Any temporary copy written to disk during rendering, and the output file kept available for download, is deleted automatically within 24 hours of the job finishing. We do not open, read, index or analyse uploaded content, do not use it to train or improve models, and do not share it with anyone. Rendering servers are located in the United States; if you need a different region, contact us.

5. How we use data

Account and entitlement data are used to sign you in, to apply the plan you bought across your devices, to send receipts and renewal notices, and to answer support requests. Usage events and error reports are used to fix bugs, to decide which features to build, and to measure whether pages work; they are analysed in aggregate. We do not build advertising profiles and we do not send marketing email unless you opted in on the account page, in which case every message has an unsubscribe link.

6. The browser extension

This section is the disclosure required by the Chrome Web Store and Microsoft Edge Add-ons policies.

• Sites: the extension's content script runs only on chatgpt.com, chat.openai.com, claude.ai, gemini.google.com and chat.deepseek.com. It is not injected on any other site.
• Permissions: activeTab to read the answer you clicked Export on, in the current tab, after you click; storage to save your preferences and cache your plan status locally; contextMenus to offer Convert to Word on selected text; identity to sign in, used only when you choose to sign in.
• Data handled: the text of the answer you export is read from the page and converted inside the extension. For Word and rich-text output it is not transmitted anywhere.
• Network requests the extension makes: exactly three kinds, and no others. (1) Sign-in and plan checks, sent to our authentication provider when you choose to sign in. (2) Server-side PDF (Pro): if you ask for a PDF, the Markdown of that one answer is sent to our conversion endpoint over TLS and the PDF is returned; it is deleted as described in section 4. (3) A plain GET for a public JSON file of CSS selectors, so that a redesign of a chat site can be fixed without a store update. That request carries no account, no page content and no identifier, and the file is data, never code.
• Usage analytics: none. The extension records no clicks, no keystrokes and no usage events, sends no analytics of any kind, and contains no analytics or crash-reporting SDK. Because there is nothing to switch off, the popup has no analytics setting. The anonymous events in section 2.3 belong to the website and the web app only. This matches the "User activity: No" answer on our Chrome Web Store and Edge Add-ons data-use forms.
• Remote code: none. All executable code ships inside the extension package and is reviewed by the store.
• Use of data: we do not sell user data, do not use it for purposes unrelated to the extension's single purpose (converting page content to documents), and do not use it to determine creditworthiness or for lending.

7. Third parties we share data with

Provider	Purpose	Data
Supabase	Authentication, account database and entitlement storage	Email, sign-in provider ID, account ID, plan and subscription status, presets you save, conversion history for Pro users (file names and options, not content)
Payment service provider	Checkout, card processing, invoicing, tax, subscription billing	Email, billing country, card details (entered on their page, never seen by us), purchase history
Google (sign-in)	Optional "Sign in with Google"	Your Google account email and ID, only if you choose this method
Google Analytics 4 and Baidu Analytics (when configured and accepted)	Optional website and web app traffic and conversion measurement	Page paths, event names, output format or feature name, browser and network information, analytics cookie identifiers; no document contents
Google Fonts	Serving the Inter typeface on the website	Your browser sends a standard font request, including IP address, to Google's servers; Google states it does not use these for tracking
Hosting and email delivery providers	Running the website and sending sign-in links and receipts	Server logs as in section 2.5; email address and message content for transactional email

Each provider processes data under a contract that limits use to providing the service to us. We do not use advertising networks, analytics services that build cross-site profiles, or social media pixels. We may disclose data if required by law or to protect the service from abuse, and we will tell you if we are permitted to.

8. Cookies and local storage

The website sets no advertising or cross-site tracking cookies. We use browser storage as follows:

• localStorage holds your sign-in session token (only if you sign in), your converter preferences such as font and paper size, whether you dismissed the one-time Pro tip, and your analytics consent choice.
• If you accept optional analytics, Google Analytics and Baidu Analytics may set first-party analytics cookies. Analytics preferences lets you withdraw consent; this stops future analytics loading. You can remove existing cookies by clearing site data.
• A session cookie may be set by our payment provider during checkout, on their domain.
• The extension uses chrome.storage.local for your sign-in session and preferences, a cached copy of your plan status, an unsent draft in the popup, and the public selector file from section 6, which it keeps for 24 hours. None of these are usage records and none of them are sent back to us.

When optional analytics is configured, the site shows an Accept analytics / Decline choice before loading it. Essential converter and sign-in storage works independently of that choice. Clearing site data removes locally stored choices and cookies.

9. Retention

• Account and entitlement data: for as long as the account exists, then deleted within 30 days of a deletion request. Billing records are kept for the period required by tax law (typically 7 years) in the payment provider's system.
• Uploaded content for Pro server features and the API: deleted within 24 hours.
• Usage events and error reports: 13 months, then deleted or reduced to aggregate counts.
• Server access logs: 30 days.
• Support email: up to 12 months after the issue is closed.

10. Your rights

Wherever you live, you can ask us to show you the data we hold about you, to correct it, to export it in a machine-readable form, to delete it, or to stop processing it for a particular purpose. You can delete your account yourself from the account page, which removes account, entitlement, preset and history data immediately and cancels any subscription at the end of its period. On the website you can decline optional analytics through Analytics preferences or the Global Privacy Control / Do Not Track browser setting; the extension records none, so there is nothing to opt out of there. To exercise any other right, email [email protected] from the address on the account; we respond within 30 days. If you are in the EU, UK or Switzerland you also have the right to complain to your local data protection authority; residents of California and other US states with privacy laws have the rights those laws grant, and we do not sell or share personal information as those laws define it.

11. Legal basis (EU/UK)

We process account and billing data to perform our contract with you; optional third-party analytics with your consent; basic service events, error reports and server logs on the basis of our legitimate interest in running and improving a secure service, which you can object to; and marketing email only with your consent.

12. International transfers

Our servers and providers are located in the United States and the European Union. Where data about EU or UK residents is transferred to the US, it is covered by the providers' Standard Contractual Clauses or Data Privacy Framework certification.

13. Security

All traffic uses TLS. Account data is stored with row-level security so that a signed-in user can read only their own rows. Sign-in uses one-time email links or OAuth; we hold no passwords. Access to production systems is limited to the engineers who operate them and is logged. No system is perfectly secure; if we learn of a breach affecting your data we will notify you and any required authority without undue delay.

14. Children

MDtoDOCX is not directed at children under 16 and we do not knowingly collect data from them. If you believe a child has created an account, contact us and we will delete it.

15. Changes to this policy

We will post any change on this page and update the effective date. If a change reduces your rights or expands what we collect, we will email account holders at least 14 days before it takes effect. Previous versions are available on request.

16. Contact

MDtoDOCX, [email protected]. Use the subject line "Privacy" for requests about your data so that they are routed correctly. See also the Terms of Service, the extension page for the permission list, and Support for anything else.