Zlet Converter
The core conversion flow processes document files on the device. No cloud processing is required for conversion.
Security & privacy
Zlet Converter processes document files locally.
The core Zlet Converter workflow runs on the user’s device and does not require cloud processing for document conversion. The zlet.app website separately uses Yandex.Metrika for visit statistics.
Product files and website analytics are separate data flows.
Local processing describes how Zlet Converter handles document files. It does not mean that zlet.app is analytics-free.
zlet.app
The website uses Yandex.Metrika for visit statistics. Website analytics are separate from Converter file processing.
Other Zlet products
Each product should document its own storage, network and account behavior rather than inheriting claims from Converter.
How Zlet Converter handles a document.
The core workflow is: select local files, convert them on the device, inspect quality locally, then choose where to save the Markdown output.
01
Add
You select local files or a local folder.
02
Convert
The core conversion work runs locally on the device.
03
Check
Quality status and evidence remain part of the local workflow.
04
Export
You choose where the resulting Markdown and related assets are saved.
Current security and privacy facts.
These statements are scoped to current product behavior and the current website analytics configuration.
Local file processing
Zlet Converter processes document files locally in its core conversion flow.
Website analytics
zlet.app uses Yandex.Metrika for visit statistics.
No inherited claims
Zlet Tab and future products must document their own storage and network behavior.
Quality status is separate from conversion status
A completed conversion is not automatically presented as a quality-approved result.
Report a security issue
Do not put sensitive exploit details into a public feedback message. Use the technical issue path and keep reproduction data minimal.