Why is providing a mechanism to view your own data a security risk? You cannot view application data (even in a read only fashion) without root on android. Why should the app be able to read its own data, but the human not able to?
Why is providing a mechanism to view your own data a security risk? You cannot view application data (even in a read only fashion) without root on android. Why should the app be able to read its own data, but the human not able to?
GrapheneOS already ships Seedvault, which extracts application data with no root at all, so what you describe is possible in at least some form, but I assume not with the ergonomics you want.
Providing a good interface for that access is a specific missing capability. But we shouldn't presuppose that the only way to supply it is a global su. The former is a bounded fix; the latter changes the isolation model of the entire system. A portal is mediated, scoped to what you asked for, and revocable. Root is none of those things.
Seedvault is itself an example. The need for backups can be met either with a narrow backup service or by handing out root and letting you do it however you like. Those two have very different security properties, and you can want the new capability without wanting a generic privilege escalation path to deliver it.