Privacy policy

Last updated 9 November 2026

Katari keeps your library, reading and watching progress, history, downloads, backups and settings on your device. It has no accounts, and no server of its own that receives them. This page lists everything that leaves your device, where it goes, and how to stop it.

Crash logs and usage data

Only Katari and Katari for Linux as released on GitHub send them. Katari FOSS and builds made from the source code send nothing.

Two switches decide what is sent. Setup shows them, and you can change them any time in Settings › Security and privacy:

• Send crash logs is on until you turn it off.
• Allow analytics is off until you turn it on.

With both off, Katari sends nothing. Turning a switch off stops what it covers from then on.

What they contain

• Crash logs: the error and where in Katari's code it happened, including when Katari stops responding. An error's message can include what Katari was working on, such as a web address from a source.
• Usage data: when Katari is installed, updated, opened and put in the background.
• Both: the screen that was showing and the kind of entry it was about, such as a comic or a video, but never its title. Katari's version. Your device's maker and model, system version, language and screen size, and on Android its network type and mobile carrier. On Linux, the distribution, the desktop and the session type.
• A random identifier created on your device, so that reports from one installation can be told apart. It is not linked to your name, an email address or any account. Clearing Katari's data or installing it again creates a new one.

Where they go

Reports go to PostHog, a product analytics service, and are stored in its EU cloud. PostHog works out an approximate location, the country and city, from the IP address a report comes from, then discards the address without storing it. PostHog's privacy policy covers how it handles them.

Only Katari's developer reads them, to find and fix problems and to learn which parts of the app are used. They are not sold, shared with anyone else or used for advertising.

Connections you choose

Everything else Katari sends goes only where you point it, or to a service you turn on.

• Extensions connect to the sites they read comics, books and videos from, and the extension stores you add send their list of extensions. Katari doesn't run those sites; their own privacy policies apply. Cookies they set stay on your device.
• Sync sends your library, progress, history and settings only to the sync server you run yourself.
• Check for updates on launch, in Settings › About, asks GitHub for the newest release when Katari opens and every 6 hours while it stays open. Updates download from GitHub too. GitHub's privacy statement applies.
• Settings › Players › Anime player › Find intro and credits times online is off until you turn it on. Then, when a source marks no intro or credits, Katari sends the series title and episode number to the services you leave on below it: AniSkip, which it finds the series for through AniList, and TheIntroDB, through TVmaze and Wikidata.
• Translation with a DeepL-compatible server or a LibreTranslate Server sends the text to that server. Katari asks you to accept the engine's privacy disclosure before it translates anything. The other engines translate on the device.
• Text recognition reads pages on the device, with models downloaded once from Hugging Face.
• Text to speech uses the voices your system provides. A network voice sends the text to its engine's service.
• Settings › Advanced › DNS over HTTPS (DoH) is off until you pick a provider. Then that provider learns the names of the sites Katari connects to.

This website

This website uses no cookies, analytics or trackers. If you pick a theme, your browser remembers it, and it never leaves your browser. GitHub hosts the site, and GitHub's privacy statement covers what it logs about visits.

Changes and questions

When what Katari sends changes, this page changes with it. Ask about anything here by opening an issue on GitHub.