Privacy Policy
Doc-HTML-Translate does not collect, store, log, or transmit any personal data. It runs entirely on your device, has no servers of its own, and contains no telemetry, analytics, ads, or accounts.
What it accesses and why
- The document files you open - to convert them to local HTML.
- Your web browser - to display the converted HTML.
- The internet - only if you explicitly choose Google translation: the extracted text is sent to the Google Cloud Translation API using a key you supply. With the local Ollama option, text is sent only to a translation server running on your own machine. With the default free browser translation, nothing is sent by the app at all.
Local files it writes
The converted HTML output (next to the source file, or in a folder you choose), and an optional API key file you place yourself. These never leave your device.
Sending logs to the author
The app keeps its recent run logs on your own disk and, only when you ask for it
(the Send logs to the author button in the About section, or -report on the
command line), packs them with a short environment summary - version, edition, platform, interface
language, whether OCR is available - and the last run's settings into one archive under
%LOCALAPPDATA%\doc-html-translate\reports\. Anything that looks like a key, a token, a
password or a Google API key becomes <redacted> before it reaches the archive, and
your folder paths are reduced to %USERPROFILE% and %LOCALAPPDATA%. The
Google Cloud Translation API key is never in it.
The archive stays on your disk. The app never uploads it and opens no network connection for it. It opens the archive's folder, puts the path on your clipboard, and composes an unsent message in your own mail program addressed to the author - you attach the archive and press Send yourself, and you can open the archive first or clear the stored logs at any time.
Data sharing
None. Children: no data collected. The app is open source - you can audit exactly what it does.