Certainly there's little to no practical risk in this particular case, but that doesn't make the policy ok. It would really suck if accepting this signaled that

Certainly there's little to no practical risk in this particular case, but that doesn't make the policy ok. It would really suck if accepting this signaled that it's ok to make such policies for closed-source software, for example, eventually leading to the legitimizing and normalization of keyloggers and/or other spyware-like behavior under the excuse that law enforcement may eventually want it. What really irks here is saying that such a policy is normal now and therefore ok, when it's obviously a large new overreach. The response that it's OK if they say they'll behave like spyware because there's little chance they'll succeed also irks. But worse are the multiple people saying that people can't recognize a standard policy boilerplate when it obviously is not. If we're being really generous, it's possible that the current wording was not intended to mean what it says, but that also doesn't make it ok.