5 ms·

> In the case of Pixel 4, the model runs on device, never sends sensor data to Google servers, and helps it interpret the motion to Quick Gestures. From the "T

> In the case of Pixel 4, the model runs on device, never sends sensor data to Google servers, and helps it interpret the motion to Quick Gestures. From the "Technology" page linked at the top. Personally, I don't see how it is meaningfully any worse for privacy than the always on microphone in the google assistant. And I look forward to what it will enable for VR and AR tech!

schmichael 7y ago
"Never sending raw sensor data to Google" and "Never sending inferences made from sensor data to Google" are massively different claims. "Never sending raw sensor data to Google" is an efficiency claim that means little with regard to protecting privacy.
- drusepth 7y ago
  It's pretty trivial* to sniff traffic and find out what data is actually being sent to Google once people have devices in their hands, no? It doesn't seem like the kind of thing a company would try to underhandedly sneak in after explicitly saying the sensor runs on-device and "never sends sensor data to Google servers". * Trivial in the sense of someone who actually knows what they're doing -- of which we only really need one person in order to "leak" what's actually happening.
  - victoro0 7y ago
    Are you serious? Because I'm pretty sure there is some random "user experience checkbox" checked by default that somehow means some of the data is sent to Google so they can "improve their products and services" and what not, but don't worry because it is probably "anonymized" and will only be seen by "humans" or "AIs" depending on what feels less bad for the general public once discovered.
  - Arelius 7y ago
    No, it's not. Between encryption and a high background communication noise of the cellphone already it's hard to discern exactly what is being sent. I don't think anyone thinks that they are, or will be sending all the sensor data to the servers. But they don't need to, they only need to send back what is determined due to that data. Specifically consider what is most likely for an ad company, a few differentiated markers to help with targeting, that can easily be packed into a few bits. And can be trivially stored to be sent later on with some other packet that has a valid reason to be sent. (Appstore update check, anyone?) Accounting for every bit that leaves the phone sounds like a nigh impossible task. I'm not saying this is definitely happening, but I don't think it's practical to rule out the possibility, with any amount of packet sniffing.
kabacha 7y ago
> the model runs on device, never sends sensor data to Google servers Would you by any chance be interested in buying a bridge in Brooklyn?

schmichael 7y ago

"Never sending raw sensor data to Google" and "Never sending inferences made from sensor data to Google" are massively different claims. "Never sending raw sensor data to Google" is an efficiency claim that means little with regard to protecting privacy.

drusepth 7y ago
It's pretty trivial* to sniff traffic and find out what data is actually being sent to Google once people have devices in their hands, no? It doesn't seem like the kind of thing a company would try to underhandedly sneak in after explicitly saying the sensor runs on-device and "never sends sensor data to Google servers". * Trivial in the sense of someone who actually knows what they're doing -- of which we only really need one person in order to "leak" what's actually happening.
- victoro0 7y ago
  Are you serious? Because I'm pretty sure there is some random "user experience checkbox" checked by default that somehow means some of the data is sent to Google so they can "improve their products and services" and what not, but don't worry because it is probably "anonymized" and will only be seen by "humans" or "AIs" depending on what feels less bad for the general public once discovered.
- Arelius 7y ago
  No, it's not. Between encryption and a high background communication noise of the cellphone already it's hard to discern exactly what is being sent. I don't think anyone thinks that they are, or will be sending all the sensor data to the servers. But they don't need to, they only need to send back what is determined due to that data. Specifically consider what is most likely for an ad company, a few differentiated markers to help with targeting, that can easily be packed into a few bits. And can be trivially stored to be sent later on with some other packet that has a valid reason to be sent. (Appstore update check, anyone?) Accounting for every bit that leaves the phone sounds like a nigh impossible task. I'm not saying this is definitely happening, but I don't think it's practical to rule out the possibility, with any amount of packet sniffing.

kabacha 7y ago

> the model runs on device, never sends sensor data to Google servers Would you by any chance be interested in buying a bridge in Brooklyn?