Privacy Principles
Effective date: July 1, 2026 · Version 1.0
1. Defaults over disclosures
A privacy setting buried in a menu, defaulted to the less private option, is not meaningfully a choice. Kairon ships the private option on and lets you opt out, not the other way around.
2. Minimize before you protect
The safest data is data never collected. We ask, for every feature, whether it needs to leave the device at all before we ask how to secure it in transit.
3. Verifiable, not just promised
Where possible, the components that make privacy claims (tracker blocking, sync encryption) are open source, so the claim can be checked against the code.
4. No dark patterns
We don't use confusing toggles, pre-checked boxes, or reward loops to push you toward sharing more than you intend to.
5. Business model independence
Kairon is not funded by advertising, and browsing data is not the product being monetized. Revenue comes from optional paid sync tiers and the extension store.