3 ms·
Howdy! Wanted to help share some context as I'm the Head of Product for Neeva. First, thank you for this feedback and everyone else's in the thread, as well. W
by ahvee_at_neeva 6y ago
Howdy! Wanted to help share some context as I'm the Head of Product for Neeva.
First, thank you for this feedback and everyone else's in the thread, as well. We are listening and improving based on what we hear from our early users and all those interested in our work.
For context on some of the choices we made when thinking about building a private search engine:
- First, one of the biggest risks to people’s privacy online is advertising. To present a true alternative requires an alternative source of revenue than advertisers. By being a subscription service we only put users first.
- Second, a search engine that stores nothing can’t get better. Even on this thread people have preferences like wanting to never see Pinterest results or see more of them. We want to offer a better search experience and privacy so you don’t have to choose one or the other.
Unfortunately, we can’t build all things ourselves to get there. Whenever we work with a partner, we are very careful to ensure that they see only as little as they need to see. For example, while we do use Stripe to process credit card payments, they are never going to see what anyone searched on Neeva. However, in order to cover the full, diverse spectrum of what people search we have partners like Yelp, Xignite and Bing in addition to our own tech. Given what’s required, there isn’t a viable, private search engine that exists without such partners, as well. Whether others disclose them is another question. Particularly the advertising partners of the “free” search engines...
In each of these cases, we vet the privacy standards of these businesses and make sure they align with our privacy policy and values, as well. In cases like Bing we take proactive measures to protect user privacy by obfuscating or omitting all other personal information outside of a query.
Therefore, clauses like the above are meant to help bring transparency more than anything.
Lastly, in terms of aggregated and de-identified information, we’ll take another look at this language. We've already updated our policy based on user feedback and we have no intention of ever sharing de-identified information like the above. Thanks for the callout.
Keep the feedback coming! We're listening. This is hard stuff and we appreciate all the support we receive.