Google monitors and restricts shared content. This is reasonable, IMO. If someone is hosting documents publicly on the Google domain, it's reasonable for them to make judgment calls about what can and cannot be hosted.
Note that the file wasn't removed, it just had public sharing and other public features restricted. (Read the dialog in the Tweet closely)
Does it monitor only shared content?
If the author is to be believed, and if Google made a judgement call as you suggest, it is bad judgement.
I'm not concerned about happens after Google reads the document. I'm concerned that Google reads the document, and I want to know which ones are read.
Not exactly what your scenario is, but damn close: https://boingboing.net/2007/12/06/western-digital-netw.html
I can't believe it's been 15 years. I remember this like it was yesterday, and it's still the reason I won't buy anything from WD.
On a related note, back in 2007 Western Digital did indeed decide to do some pro-active policing with users files:
https://www.theregister.com/2007/12/07/western_digital_drm_c...
And yeah, that was about as popular as you'd expect. ;)
E2E encrypted services are the exception, not the rule. This mischaracterization extends so far that when Apple announced plans to turn on E2EE for photos (necessitating an on-device scanning tool for banned photos before upload), the uproar against it was vast and unanimous. So now we still have the same photo scanning on Apple's servers, and no E2EE.