3 ms·
> Kagi does not log and associate searches with an account. https://kagi.com/privacy https://kagi.com/privacy
by frereubu 2y ago
> Kagi does not log and associate searches with an account.
https://kagi.com/privacy https://kagi.com/privacy
- roenxi 2y agoGoogle: Don't be Evil. Although I'm having some trouble finding a reference on their website to back that up. If you're going to start trusting search engine companies then maybe don't have them linked to your bank account. They can put what they like in a policy document but the problem is what happens when they decide to start doing things differently.
- dizhn 2y agoReal privacy oriented solutions REMOVE their ABILITY to keep your data. This is the reason I will probably never use Kagi. I am not logging into a search engine. Period. (I know this is futile,but it's the principle of the thing. And I don't want this to be more commonplace than it already is.)
- g_p 2y agoYou might find Privacy Pass of interest then - https://help.kagi.com/kagi/privacy/privacy-pass.html https://help.kagi.com/kagi/privacy/privacy-pass.html It should be out in the next day or so.
- promiseofbeans 2y agoOoh this is interesting. Theoretically these could still be associated with my account right? Since you need to use my session token to generate these privacy tokens. Is there a technical explainer somewhere with instructions for setting this up without a web extension? Edit: Looking into it, it seems like this uses the same mechanism for tokens as Cloudflare's turnstile system: https://privacypass.github.io/ https://privacypass.github.io/ or for the proper standard https://www.rfc-editor.org/rfc/rfc9578.html https://www.rfc-editor.org/rfc/rfc9578.html Excerpt that explains how it works: > When an internet challenge is solved correctly by a user, Privacy Pass will generate a number of random nonces that will be used as tokens. These tokens will be cryptographically blinded and then sent to the challenge provider. If the solution is valid, the provider will sign the blinded tokens and return them to the client. Privacy Pass will unblind the tokens and store them for future use. So it seems like as long as the cryptography is done right and Kagi's webextension does what it says, they are actually private.
- dizhn 2y agoThis is very exciting new stuff. I am sure it'll find a million other uses.
- dizhn 2y agoAwesome. I didn't see much detail about how it works in the page. Something like this would be useful for other sites as well. Is this using an existing technology? (Firefox extension is not found. It's probably not in the store yet. Can't find with search either.)
- promiseofbeans 2y agoLooks like they're implementing this, which is also used by Cloudflare Turnstile: https://privacypass.github.io/ https://privacypass.github.io/ The standard has also been published as RFC9578: https://www.rfc-editor.org/rfc/rfc9578.html https://www.rfc-editor.org/rfc/rfc9578.html
- freediver 2y agoWe didn't launch this yet. It is in testing which is why we published this doc for testers. Full blog post with complete run down of the tech and implementation coming (very) soon.
- tomcatfish 2y agoHoly crap this is going to let me move some privacy-focused folks over to join me in Kagitopia. Good job guys, you are always working on something cool.