Can you be more specific (scenario/user story)? This would be where an existing site has existing infrastructure in place to put and fetch data on the server at the operator’s expense rather than the accountholder (user). The user would still need an account with an off-site remoteStorage provider and elect to store and retrieve their data from there, rather than (or in addition to) the website operator’s S3/R2 buckets. The fact that the browser-based app is actually storing the data with the user’s remoteStorage provider is not meant to be transparent to the user.