1. Summary
- Everything you type into the editors, converters, and generators is processed in your browser and is never uploaded to us.
- The Chrome extension works the same way: the popup editor, page converter, and HTML-to-Markdown conversion all run locally. The extension reads a page only when you click its context-menu item, and it contains no analytics or tracking of its own.
- There are no accounts, so we hold no profiles, passwords, or usage histories.
- Drafts, your saved document library, offline files, and your theme preference are stored on your own device and can be deleted by clearing site data. The extension stores its popup draft in Chrome's local extension storage.
- The only information you actively send us is what you type into the contact form; Google Analytics data is automatically sent to Google to measure aggregate website use. The extension does not use Google Analytics.
2. Who we are
Markdown Editor AI operates the website at https://markdowneditorai.com/ and is the data controller for the limited personal data described in this policy. You can reach us through the contact page.
3. Your documents
The Markdown editor, Discord editor, table generator, PDF exporter, HTML converters, and every other tool on this site run as client-side code. Parsing, previewing, converting, and file generation all happen inside your browser tab. Your text is not transmitted to our servers, is not logged, and is not shared with any third party for processing. Exported files are assembled locally and saved by your browser's own download mechanism.
A practical way to confirm this: load any tool page, disconnect from the network, and keep working. The tools continue to function because there is nothing to send.
Two features move content only when you ask them to. A share link stores the compressed document in the URL fragment (after #share=), which browsers do not send to our servers, but anyone you give the link to can read the document. The Discord embed builder posts your message directly from your browser to the Discord webhook URL you provide, and only when you press send; that content is then handled under Discord's own terms.
Chrome extension
The Chrome extension follows the same local-only model. Its popup Markdown editor and the HTML-to-Markdown converter both run entirely inside the extension — no content is sent to our servers or to any third party.
When you right-click and choose "Convert selection to Markdown" or "Convert page to Markdown", the extension uses Chrome's activeTab and scripting permissions to inject a one-off function that reads the HTML you selected (or the page's main content). This happens only when you explicitly click the menu item — the extension never reads pages in the background or without your action. The captured HTML is held in Chrome's ephemeral session storage under a random identifier, consumed once by the conversion tab, and immediately deleted. It does not survive a browser restart.
Before conversion, all captured HTML is sanitised with DOMPurify: scripts, iframes, forms, event handlers, and other unsafe markup are stripped. The clean HTML is then converted to Markdown locally using Turndown, and you can copy, download, or edit the result.
4. Browser storage
We use your browser's local storage, IndexedDB, and Cache Storage — not cookies — for the following:
- Draft autosave. Editor content is saved under keys beginning with
mdai:draft:so a refresh or accidental tab close does not lose your work. - Theme preference. A
themekey records whether you chose light mode, so the site does not flash the wrong colours on the next visit. - Document library. Documents you save in the Markdown editor are kept in an IndexedDB database named
mdai, with the active document's ID stored undermdai:active-document. - Offline cache. A service worker saves copies of the site's own pages and files in Cache Storage so the tools keep working without a connection. It contains no document content.
Chrome extension storage
The Chrome extension uses Chrome's own extension storage APIs, which are separate from the website's storage:
- Popup draft. The text you type in the extension's popup editor is saved in
chrome.storage.localunder adraftkey so it persists between popup sessions. It stays on your device and is never sent to us. - Page capture (ephemeral). When you convert a page or selection to Markdown, the captured HTML is held briefly in
chrome.storage.sessionunder a random identifier. It is consumed once by the conversion tab, immediately deleted, and does not survive a browser restart.
All of these values stay on your device and are never sent to us. For the website, remove stored data at any time by clearing site data for this domain in your browser settings; private or incognito windows discard them automatically when the window closes. For the extension, you can clear its data by removing the extension from Chrome or by using Chrome's extension storage controls.
5. Contact form
If you write to us through the contact page, we receive the name, email address, topic, and message you submit. We use that information only to understand and respond to your enquiry, and to keep a record of the issue if it leads to a fix.
Submissions are delivered by Web3Forms, a form-to-email provider that processes the submission on our behalf in order to forward it to our inbox. Please do not include confidential documents, credentials, or sensitive personal data in a message.
6. Hosting and server logs
The site is served as static files from a third-party hosting and content-delivery provider. Like any web host, that provider processes technical request data such as your IP address, user agent, requested URL, and timestamp in order to deliver pages and to protect the service against abuse. This is standard infrastructure logging performed by the provider, and it never includes the contents of your documents.
7. Analytics
The site uses Google Analytics 4 to measure aggregate use of the website and improve its tools. Google Analytics may collect page views, referring pages, approximate location, device and browser information, and online identifiers such as cookie identifiers. It does not receive the documents or text you enter into the tools. Google processes this information under its own terms and privacy policy.
Google Analytics is loaded automatically when you visit the site. No consent is requested before the analytics script runs. If you do not wish to be measured, you can use a browser extension such as the Google Analytics Opt-out Browser Add-on or enable a tracking-protection feature in your browser.
The Chrome extension does not include Google Analytics or any other analytics, telemetry, or tracking code. It makes no network requests of its own.
9. Third parties
The third parties involved in running this site are our hosting and content-delivery provider, Google Analytics, which loads automatically when you visit, and our form-delivery provider when you use the contact form. We do not sell or rent personal data, and we do not use Google Analytics for advertising or cross-site marketing audiences. Pages link to external documentation and platforms such as Discord and GitHub; once you follow a link, that site's own privacy policy applies.
The Chrome extension does not communicate with any third-party service. When you click a link inside the extension (such as "Open full editor" or a tool link), you navigate to markdowneditorai.com in a normal browser tab, at which point the website's own third-party integrations described above apply.
10. Legal basis
Where the GDPR applies, we rely on our legitimate interests in operating and securing the website and understanding aggregate website use to improve our tools, where permitted by applicable law. We rely on the steps you take to send a contact message to process that enquiry. Where the CCPA or similar laws apply, note that we do not sell personal information or share it for cross-context behavioural advertising.
11. Data retention
Contact messages are kept only as long as they are useful for handling your enquiry and any follow-up, and are deleted on request. Server logs are retained by the hosting provider for a short period under its own retention schedule. Google Analytics data is retained according to the configured Google Analytics data retention setting. Drafts and preferences live on your device and are retained until you clear them; we have no copy and therefore nothing to delete on our side.
12. Your rights
Depending on where you live, you may have the right to access, correct, delete, or export the personal data we hold about you, to object to or restrict its processing, and to withdraw consent where processing is based on consent. Analytics requests may also need to be directed to Google because Google processes the analytics data. Email us and we will act on requests about data we control, normally within thirty days. You also have the right to complain to your local data protection authority.
13. Children
The Service is not directed at children under 13, and we do not knowingly collect their personal data. If you believe a child has sent us personal information through the contact form, let us know and we will delete it.
14. Security
The site is served over HTTPS, rendered content is passed through a sanitizer before it is displayed, and raw HTML in Markdown stays disabled unless you explicitly enable it. Keeping documents on your own device is itself the strongest protection we can offer: data that is never transmitted cannot be intercepted or breached in transit. No method of transmission or storage is completely secure, so please use your own judgement with genuinely sensitive material.
The Chrome extension applies the same sanitisation approach: all captured HTML is processed through DOMPurify before conversion, stripping scripts, iframes, forms, inline event handlers, and other unsafe markup. The extension requests only the minimum permissions it needs (activeTab, scripting, contextMenus, and storage) and never reads a page without your explicit action.
15. Changes to this policy
We will update this page when our practices change — for example if our analytics practices change or a provider is replaced. The revised policy takes effect when published, and the "last updated" date above will change accordingly. Material changes will be described in the relevant section rather than buried in a rewrite.
16. Contact
Privacy questions and data requests can be sent through the contact page. Our terms and conditions cover the rules for using the tools themselves.
This policy is provided for general information and is not legal advice.