Yes, yes. I understand the concept, however there is a world of difference between information on my preferences being only accessible by me vs by Veews server vs by anyone. There are also vast differences and considerations on technical side. F.e. if information were to remain private, it would need to be all collected client side, sharing it between different devices I might be using would require some communication and storage (encrypted custom json?). All that trouble disappears when it is Veews server that collects the data and it should be considerably cheaper to operate that way. Some functions are either not feasible or not possible at all in "privacy model". F.e. it might be ok to run some AI data collector on a smartphone, however it would never be possible to implement something that requires big-data crunch, and not just because smartphone is too weak to handle the data, but because you wouldn't even have access to other people's data in such model (example: "other people like you were also interested in..." requires access to info on other people).
I'm not saying "privacy model" is superior to "centralized entity model" or "public model". After all the first one is least efficient but offers best privacy, centralized one is most efficient but offers only pseudo-privacy and is most susceptible to interruptions, while public model offers best accessibility at total expense of privacy.
I think it is important for users to know the difference and to know what kind of model is implemented with the tools they are using. Yeah, it sounds strange when we are talking about Hive, where very sensitive financial information is out in the open and you can already profile people based on public information on what they write and vote for, who they follow or blacklist etc. :o)
There is zero financial information at all gathered by Veews, again, we literally...Take the input you give it by saying if you like something or not and then feed you content you like.