Telemetry & Diagnostics Policy

1. Default state

Kairon ships with telemetry and crash reporting disabled, and there is no setting that enables them. At startup the app disables Chromium's crash reporting, metrics, sync, translate, background networking, and component-update systems, and it cancels requests to known telemetry endpoints (such as safebrowsing.googleapis.com, clients2.google.com, and update.googleapis.com).

2. What happens instead

• Errors and uncaught exceptions are appended to a local log file (kairon-errors.log) under the app's user data folder — they never leave your machine
• No crash reports, performance counters, or usage counts are collected or transmitted

3. What's never collected

Page content, URLs visited, form input, browsing history, or any data that could reconstruct your browsing activity.

4. App-initiated network activity

The only network requests the app starts on its own are the EasyList and EasyPrivacy filter-list downloads at startup (used to compile the ad blocker) and DNS-over-HTTPS lookups when Secure DNS is enabled. Everything else originates from your own navigation.

5. Verification

Kairon's source is open. You can inspect the startup switches, the telemetry request blocker, and the local error logger in the repository, or watch the app's network traffic yourself.