I think a private and non-private option could be good. For example, Chrome has a non-private, and private sync of settings, one with a compromised UX but end-to-end encrypted, and the other with the normal UX.
Possibly - the downsides are that it adds complexity, and we would have to be very careful how we communicate it to the user, and understand the differences.
Say we add a toggle like "anonymize my domain adjustments":
We have to carefully choose the default. Do we leave it on by default? The user might get the wrong idea that it is some kind of data collection. Do we leave it off by default? Some users may never discover the usability of the "non-anonymous" mode and think the feature sucks 😄
This does not stop at domain adjustments either. All of your account settings are, naturally, associated with your account ID. Is Kagi still Kagi without all of these? Could we implement an "anonymous account" without a large portion of our features, and not make "non-anonymous", but more useful, accounts feel targeted?
The line we have chosen to walk so far is:
All of the data (settings, email) you store with us is private. This means it does not leave Kagi's servers, it is not shared with anyone besides you to fulfill the service's features.
All of your searches you perform on Kagi are anonymous. They are not associated with your account.
We could have more options geared towards true anonymity in the future - many people have requested it. For now we are focused on building a great, private product by default.