Access to user data and native vs. web are orthogonal concerns.
E.g., on iOS you don't have to give an app access to any data, but can still have the app installed -- access is a post-install, standardized dialog when the app requests permission.
Similarly you could easily invent web apis that would give access to data (like location, which already exists).
My point was that web applications would typically have access to more data per default, in a world with no native apps with all your applications in "the cloud" more of your data would likely also be in the hands of others. I don't think they are orthogonal concerns at all.
Regarding the Coding horror link here though, I do agree with the point about native applications that essentially are repackaged web pages.
Ah, I took your point to be completely the opposite! Oops.
Whether it's a native app or "in the cloud", I think most people want their data to be synched across devices, so you're going to have to trust somebody with it.
(Well, unless you're synching encrypted data, but maybe what we should all be doing, but I wouldn't hold my breath...)
E.g., on iOS you don't have to give an app access to any data, but can still have the app installed -- access is a post-install, standardized dialog when the app requests permission.
Similarly you could easily invent web apis that would give access to data (like location, which already exists).