For example, if the login requires a password and SMS 2fa, but the SMS is to a Google Fi phone number, then you're going to have to also enable the Google Fi account for that user to be able to login. Or what if they need to use email password resets to another suspended account? (remember you will probably suspend all accounts of a user at once if you suspect something illegal).
Making a special 'chat' tool inside the login flow that only requires a single factor (the account password) which allows presenting evidence to a google rep seems like the obvious solution (or requesting the account suspension be delayed, or that the data be deleted).
Building and staffing that sounds like quite a lot of work though, which would be hard to justify for the tiny number of impacted accounts and zero revenue potential.
It isn't as far as I can see.
IMO it is just Google trampling over peoples rights while trying to use a weird reading of GDPR as excuse.
I'm so ready for EU to start punishing more of the blatant abuse of GDPR that we see, especially by the big players in the market.
That works both ways - as well as not being able to get the customers permission to keep the data, they also would not be able to get the customers request to delete the data if they were to keep it 'just in case'.
Until they have built some functionality to communicate with the customer behind a suspended account, they have to delete the data within 30 days.