Was going to post this as a reply at https://github.com/kagisearch/privacypass-extension/issues/10 but I decided against it. Feel free to add it there if you agree, though.
We do plan to introduce client side settings (theming, custom css, etc), and we are also exploring allowing a select few server side settings (like safe search), at the cost of anonymity.
Could safe search be made to work client side? Obligatory I don't know what I'm talking about but could the server send results to the client with a safe/unsafe tag/property attached to each that are then filtered client-side?
Actually this may have issues as if almost all the results are unsafe, safe search enabled clients would have to load more results, which can be inferred and has the same anonymity cost as before.
But there might be a simpler, more anonymous way. Depending on the client side safe search toggle, the client either needs a batch of only safe results or a batch also including unsafe results.
If the server sends the client both sets of results, it can pick which to display and which to discard based on its setting.
I know sending double the results isn't efficien, but the initial results fetch only gets the text, links, and thumbnails for the page, right? That should all be pretty minimal, and it is a premium feature.
But even if this is adopted, please add a server side toggle until it's implemented.