What PlugGo can—and cannot—access

PlugGo uses Google’s drive.file permission. It can work with files created or deliberately opened through PlugGo, but it does not receive general permission to browse unrelated files in the sender’s Google Drive.

The shared file stays in Google Drive. PlugGo stores service data needed to run the link, such as file name, size, availability settings, recipient message and download activity.

Google access tokens are kept out of browser Web Storage, and the longer-lived Google authorization used to restore a Drive session is encrypted on the server.

A PlugGo link is unlisted but remains a bearer link: anyone who receives the valid URL may be able to open it. Current links are not end-to-end encrypted or password-protected.

Browser, PlugGo and Google Drive traffic uses HTTPS/TLS. Senders can manage availability, remove uploads and revoke PlugGo’s Google access.