Chrome is relatively limited in scope compared to, say, a user on an instance of degoogled chromium just using the same Google services along with all the other browsing they do. The extra data that’s gathered is generally going to be things like a little more DNS query information, (assuming your device isn’t already set to default to Google’s DNS server) links you visit that don’t already have Google’s trackers on them (very few) and some general information like when you’re turning on your computer and Chrome is opening up.
The real difference is in how Chrome doesn’t protect you like other browsers do, and it thus makes more of the collection that Google’s services do indirectly, possible.
Perplexity is still being pretty vague here, but if I had to guess, it would essentially just be taking all the stuff that Google would usually get from tracking pixels and ad cookies, and baking that directly in to the browser instead of it relying on individual sites using it.
Is Chrome not doing exactly this?
Chrome is relatively limited in scope compared to, say, a user on an instance of degoogled chromium just using the same Google services along with all the other browsing they do. The extra data that’s gathered is generally going to be things like a little more DNS query information, (assuming your device isn’t already set to default to Google’s DNS server) links you visit that don’t already have Google’s trackers on them (very few) and some general information like when you’re turning on your computer and Chrome is opening up.
The real difference is in how Chrome doesn’t protect you like other browsers do, and it thus makes more of the collection that Google’s services do indirectly, possible.
Perplexity is still being pretty vague here, but if I had to guess, it would essentially just be taking all the stuff that Google would usually get from tracking pixels and ad cookies, and baking that directly in to the browser instead of it relying on individual sites using it.