Privacy

Last updated: 8 October 2026

OsonKit opens files in your browser. Your files are not uploaded: their contents, names and bytes are never sent to our servers or to anyone else. This page explains how that works, which requests the site does make, and where the promise ends.

What happens to your file

  • When you choose, drop or paste a file, your browser reads it on your device. Parsing runs in this page and in background workers of this page.
  • If that changes, this page will be updated first. Analytics would only count interface events and would never include file names, contents or addresses of opened files. Ads will appear only on guide pages, where no file can be opened: the page where you open a file never loads ad scripts, and going from a guide to it always loads the page anew. The ad networks (Google AdSense, Yandex Advertising Network) may use cookies — where the law requires it, only with your consent.
  • The file is kept only in the memory of the open tab. Closing the file or the tab discards it; nothing is saved on the server. The one exception is described below: reloading for a new version of OsonKit.
  • “Download original” saves the same file from memory back to your device. “Print” uses your browser’s print dialog.

Requests the site makes

  • Loading OsonKit downloads its own pages, scripts, styles and fonts from this website. Fonts are hosted here; there are no requests to font or CDN services.
  • When a PDF needs them, the viewer downloads helper files from this website by name — for example a character map for Japanese text or a decoder for a special image format. The request names only that helper file and carries nothing from your document.
  • The site may prefetch its own pages (such as this one) so that links open faster.
  • As with any website, the hosting provider may record standard request details for these downloads: IP address, browser, time and the page address. These records never contain your files.
  • Cloudflare, which hosts this site, counts visits with Cloudflare Web Analytics: a small script from static.cloudflareinsights.com sends the page address, where you came from and how fast the page loaded. It sets no cookies and collects nothing about your files.

What is stored on your device

  • Your theme (light or dark) and the language you picked, in your browser’s local storage. No cookies.
  • A copy of the site’s own pages, scripts, fonts and decoders, in your browser’s cache, so the viewers open without an internet connection. Your files are never put there. Clearing the site data in your browser removes it.
  • When a new version of OsonKit is ready and you press “Reload” with a file open, that file (up to 100 MB in total) is put into your browser’s storage on this device for the moment of the reload, opened again right after it and deleted at once. It is not sent anywhere. Larger files are not kept: open them again after the reload.

Analytics and ads

  • Visits are counted by Cloudflare Web Analytics, the analytics of our host: no cookies, no profiles, no advertising ids. It sees the page address, the referring site, your country, browser and loading speed — never your files, their names or contents.
  • Ads appear only on guide pages, where no file can be opened: the page where you open a file never loads ad scripts, and going from a guide to it always loads the page anew. The ad networks (Google AdSense, Yandex Advertising Network) may use cookies — where the law requires it, only with your consent.

Links and images inside documents

  • Pictures that a Word or Markdown document loads from the internet are blocked, so opening a document does not contact other websites.
  • Links inside a document are inactive until you click them. Web links then open in a new tab, and the other website’s own privacy policy applies. Scripts and macros in documents are never run.

Limits of the promise

  • Offline use works after the site has loaded once with a connection, in browsers that support it (all current ones). Installing OsonKit as an app adds “Open with” for files in Chrome, Edge and other Chromium browsers; the files still open only on your device.
  • Browser extensions that are allowed to read web pages can see what is displayed, as on any website. Use a private window without extensions if that matters to you.
  • What you do with the file afterwards — copying text, printing to a network or “save as PDF” service, taking screenshots — is handled by your browser, operating system or those services, not by OsonKit.