But Google (and Facebook, and probably some other companies) don't have reasonable processes for disputing or resolving these situations.
Some have said that we should consider Google's challenge: lots of users/activities that need to be monitored and policed. The assumption is that Google could not afford to do this "reasonably" with humans instead of automated systems because the volume is high.
But Google certainly could hire and train humans to follow a process for reviewing and assisting in resolving these cases. They don't. It is doubtful that they cannot afford to do this; I haven't checked their annual report lately, but I'm guessing they still have a healthy profit.
In the unlikely event that involving more humans would be too expensive, then Google should raise their prices (or stop giving so much away for free).
To summarize, there is no excuse for Google to operate this way. They do because they can, and because the damage still falls into the "acceptable losses" column.
When AWS first arrived they had the same automated support system that Google does, and they didn’t really want to comply with GDPR. We probably would’ve gone with Azure anyway because it’s the easy option for operations when you’re already in bed with 365, but the Amazon/Google attitude meant they weren’t even considered beyond the first look.
Since then AWS has overtaken Azure in GDPR compliance and the availability of their support, and we now have several supplier operated solutions in AWS.
Google is still on the “do not buy from this company” list.
But maybe they just aren’t interested. They are primarily an advertising company after all.
A couple years ago, there was an update that affected a bunch of embedded devices and caused some machines to go down. Luckily our machines were on an older version, but another shop we worked with got hit by it.
Within an hour of Microsoft being alerted to the issue they'd begun working on the problem and within two hours machines were back up and running again after Microsoft pushed an update.