Hacker News new | ask | show | jobs
by selcuka 1002 days ago
I trust you will not, but what about after you exit?

Anyway, you or someone else will probably start a new search engine, and we will start again. It's best to enjoy it until that happens.

1 comments

I believe the founder, freediver.

In the case of Radio Shack, they too made a promise never to sell or give the data to other entities. The CEO even fought for that in bankruptcy court.

The judge deemed that the user data was worth a significant sum, and the judge screwed everyone over for the debtors.

Once you capture the data, it's a toxic but valuable asset. And there's always someone willing to go to any end and use it, regardless the promises. And it may full well be someone who has power over you, and you'd never know until it's too late.

(I've done my share of medical and sensitive queries. The really sensitive ones go through I2P or Tor in a VM. I'm not willing to give that knowledge to anyone.)

> Once you capture the data, it's a toxic but valuable asset.

That is the thing, Kagi does not capture the data. Not only we do not need it, but it would just be a liability for us, with no benefit.

Please refer to our privacy policy for more details: https://kagi.com/privacy

Subscribing specifically because of this policy.
> I believe the founder, freediver.

Oh, don't get me wrong. I believe them, too. My point was if they ever sell the company, the buyer might change the privacy statement and start collecting/selling information from that point on. I didn't mean the new owners would necessarily have access to the data collected previously.

Since you're bringing up "capturing the data", it's worth pointing at Kagi's privacy policy, the very first point of which is this:

> * Searches are anonymous and private to you. Kagi does not log and associate searches with an account.

https://kagi.com/privacy

Additionally the search page itself displays this notice:

> Your searches are always private. We do not see them and they are not associated with your account

The "captured" user data you seem to be concerned about doesn't appear to actually exist in this case; the data is quite explicitly not being captured.