Privacy

Your WordPress export stays on your computer.

Your export

marklean reads and converts the export in your browser. The file, your posts and your pages are never sent to marklean or anyone else.

A live site

When you connect to a live site instead, your browser reads it straight from your site's REST API. The username and application password you enter are sent only to your site, kept in that browser tab while it is open, and never stored or sent to marklean. You can revoke the application password in WordPress when you are done.

Publishing to GitHub

If you publish to GitHub, you sign in on github.com. To finish the sign-in, marklean.com exchanges the one-time code GitHub gives your browser for an access token; that is the only time the token passes through marklean, and it is not stored or logged. Your browser then creates the repository and uploads the project to GitHub directly. marklean asks only for access to public repositories, unless you choose a private one. You can revoke the access in GitHub under Settings → Applications.

Your images

When you download the project, your browser fetches the images from your WordPress site. Many sites don’t allow that directly, so those images go through marklean’s image proxy atimg.marklean.com. The proxy only fetches images, passes them straight to your browser and keeps no copy. Like any web server, its host may keep short-lived logs of requests, including your IP address and the image address.

This website

marklean.com sets no cookies. It counts visits with Cloudflare Web Analytics, which uses no cookies and does not track you across sites: it records the page, the referring site and your browser and country, without identifying you.

Questions

marklean is open source, so you can read exactly what it does onGitHub, where you can also ask questions.