(Replying to PARENT post)
Which, IIRC, means no human is given direct access without the account holder's permission. Algorithms are allowed access, but only if they emit data that is similarly secured, or emits data in aggregate (where, I think, aggregate was defined as 100k+ users per aggregate data point)
It's extremely hard for a Googler or product team to do something directly nefarious, but you do have to trust Google's privacy infrastructure.
(Replying to PARENT post)
If both you and your correspondents do use 3rd party IM client ([1], [2], etc), then just run OTR2 or OMEMO on top of the protocol, and let google store whatever it pleases - it's not going to be much use for them.
(Replying to PARENT post)
Can we please use technical terms with precision?
You can have data encrypted at rest and in transit that is still accessible to the provider and the fact that the provider can decrypt it for processing doesn't make it any less "encrypted". There is not a total ordering of encryption or security schemes.
If you would like to say that the data isn't end-to-end encrypted such that it is opaque to the service provider -- say that. Don't say it isn't meaningfully encrypted.
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
However, it's better just to encrypt everything and not be tempted by the advertising surveillance dollars.
(Replying to PARENT post)
So, not meaningfully encrypted at all then?
One could also think of it as your private key being with (1) you, (2) Google.It's in safe hands ;-)
(Replying to PARENT post)
'using encryption that leaves the messages accessible to Googleβs algorithms' So, not meaningfully encrypted at all then?