I never read Google discriminates between paying customers before. That's such a wild accusation that it requires serious evidence.
Edit: I can reply anymore but just supply a link of data handling discrimination between paying customers because that's what you imply by "there is not difference between GSuite customers and normal gmail".
You're correct in that Google doesn't discriminate between paying and non-paying customers: It happily abuses the privacy of it's paying customers too.
Many of Google's uses of data are not specific to whether or not someone is using G Suite or consumer Gmail as far as I am aware.
Bit of advice: If you don't know something, remain silent or say you don't know or ask a question. Don't confidently assert something you just made up.
I can say one of the ones that horrified me the most shortly after I transitioned off of Gmail was Smart Reply. To my knowledge, nobody was able to confirm at the time that even paid G Suite accounts were immune to being used as training data. (If you have insight on this, let me know!)
I definitely don't want my email used to train Google's AI models, which might unpredictably cough up sensitive data since machine learning is pretty much a black box.
A big issue is that at any time, Google may introduce a new "feature" and decide to use your data to power it. I also think of how purchase data gets extracted from your receipts to store in your Google account profile and the like (https://myaccount.google.com/purchases although the text on this page has changed... did they stop?) and I feel a privacy-first service would need to at minimum have switches to control what kind of data processing is performed on their email, and default new features to be off.
I do know the answer. It's probably in the privacy policy for gsuite somewhere, but that's a long document. I'm unsure if I can share it though.
What sensitive information are you concerned about coughing up? While I haven't actually looked closely at how smart reply works, it isn't just a simple lstm on text, it tracks contextual info like recipient names, so "hey " on the first line will autocomple to "Hey Todd and Amanda" if you're sending am email to two people named Todd and Amanda.
So there's some tokenization and preprocessing happening, which would avoid most of the potential privacy issues I can think up with something like that (which are all of the form of automoplete linking your name to a private fact).
Not really. It's informative of the policies on sharing confidential information, yes.
But it has nothing to do with what the actual policy on customer data is. My guess is that you'd be pleasantly surprised be the policy. I just can't find it documented publicly anywhere, so I don't know that I can share the actual policies. There are people who's job it is to share such things, they're like account managers and support people and they have guidance on the way the things they can say. My guidance is more like "don't unless it's clearly public".
Put another way, the training on data handling is longer than the training on corporate communication. So if I'm this careful with my communication, imagine the ridiculous lengths I go to with user data safety.
