That applies to public information. But I consider an extended application domain with access control to information. In this case controlling the information host is required. It's all about the application domain you target. For sharing public static data, IPFS would do it. But that is a narrow application domain already covered by the web.
I'm arguing that anything not air-gapped is potentially public. One can encrypt, control access, and so on. But once it's out there, it's far^N more vulnerable. And of course, there's a continuum. Even air-gapped stuff can leak through side channels. And some approaches to online storage are quite robust.
Once you put something on the Internet, you no longer own it.