the "application" Pigshell (a copy of the javascript downloaded from the "site" pigshell.com and running in your browser is an instance of the "application") requests and say is granted access to your GDrive.
so all permissions/rights are associated with the running instance of the "application" pigshell in your browser - cookies apart, end of story.
other than having served the javascript, the "site" pigshell.com has no further role to play here. so you could just as well have sourced/hosted these javascripts locally.
perhaps stating the obvious here, but with the abstraction pigshell provides of resources on the web, it should be reasonably straight forward to build arbitrary "internet applications" too.
with deferred pipes, split and joins (that pigshell already provides/supports) it should be possible to implement arbitrary work/data flow definitions one desires.
coupled with psty, one could build/harness special purpose "transformers" on the web
pushing it further, one could conceive of setting up pipes between transformers on the web.
of course getting there will require significant work on a security model as well.
[and then someone will figure out a way to interject ads]
the "application" Pigshell (a copy of the javascript downloaded from the "site" pigshell.com and running in your browser is an instance of the "application") requests and say is granted access to your GDrive.
so all permissions/rights are associated with the running instance of the "application" pigshell in your browser - cookies apart, end of story.
other than having served the javascript, the "site" pigshell.com has no further role to play here. so you could just as well have sourced/hosted these javascripts locally.