Your reading, your data

What we collect

We don’t run servers for KMReader and never see your personal information. The app stores everything locally so you can enjoy multi-server support, fast loading, and uninterrupted reading.

• Komga server addresses, display names, and encrypted credentials
• Reading progress, cached images, and downloaded EPUB files
• Preferences like themes, layouts, and cache budgets

iCloud, analytics, and crash reporting are not used. We can’t view or retrieve the items listed above.

How local storage works

Sensitive details such as passwords live in Keychain, while caches and preferences are stored in KMReader’s app sandbox. Removing a server profile clears its cached pages, thumbnails, and EPUB files.

You control when to clear caches or sign out. Uninstalling the app removes everything.

Connections to your server

KMReader talks directly to the Komga servers you add. All requests stay between your Apple device and your Komga instance using HTTPS if your server supports it. We never proxy, log, or inspect that traffic.

No third-party tracking

The app ships without advertising SDKs, analytics beacons, social trackers, or data brokers. What happens in KMReader stays with you.

Managing or deleting data

Because everything lives on-device, you can:

• Log out of a server to wipe its credentials and content caches
• Use the in-app cache controls to clear pages, books, or thumbnails
• Delete the app to remove every remaining file and preference

If you reinstall KMReader, you’ll start with a clean slate.

Updates to this policy

We occasionally refine this document to reflect new features or legal requirements. When that happens, we update the date below and publish the latest version on this page.