01 What the connection does
Vault offers up to three Google Drive connections. Each is a separate connection with its own Google consent screen, so permission for one never grants another.
1.1 Import files
In Vault, choose Add files → Google Drive. Google's file picker opens and you select the files to bring in. packOS reads those files and nothing else, and saves a copy in your workspace's Vault. There it is handled exactly like an uploaded file: dieline detection, proofs, quotes and specifications. Google Docs, Sheets and Slides are copied as Word, Excel and PowerPoint files. The originals in your Drive are not changed.
1.2 Keep a folder updated (coming soon)
For teams whose design agency drops artwork into a shared folder: you choose one folder in Vault, and packOS copies new and changed files from that folder, and its subfolders, into your Vault in the background. packOS downloads files only from the folder you chose and keeps nothing from outside it. This connection is not available yet.
1.3 Send a copy (coming soon)
Send a Vault file, such as an approved proof, to a Drive folder you pick. packOS creates a new file there. It never overwrites, moves or deletes the files already in your Drive. This connection is not available yet.
02 Permissions we ask for
Google shows these permissions on its consent screen before anything is connected.
| Connection | Google permission | What Google's consent screen says |
|---|---|---|
| Import files | drive.file, openid, email | See, edit, create and delete only the specific Google Drive files you use with this app; your email address |
| Keep a folder updated (coming soon) | drive.readonly, openid, email | See and download all your Google Drive files; your email address |
| Send a copy (coming soon) | drive.file, openid, email | See, edit, create and delete only the specific Google Drive files you use with this app; your email address |
Why these. drive.file only covers files you pick in Google's file picker, or that packOS
created for you. Picking a folder does not give access to the files inside it or to files added later, so keeping
a folder updated needs drive.readonly. That permission lets an app read any file your account can
see. packOS uses it only to list and download the folder you chose, and it never writes through that connection.
Someone who only imports files is never asked for it. openid and email tell us which
Google account is connected, so Vault can show it to you and a reconnect cannot silently switch accounts.
03 How your Drive data is handled
- What we read. The files you pick, or, for a folder you keep updated, the files in that folder: their contents, names, sizes, types and revision details.
- Where it goes. Copies are saved in your workspace's private Vault. Members of that workspace can see them according to its permissions.
- Tokens. To keep a connection working, packOS stores an encrypted refresh token on our servers, sealed with your company's own key. It is never sent to your browser. Short-lived access tokens are not stored. The one exception is Google's file picker, which runs in your browser with a short-lived token limited to the files you pick.
- Never for advertising or AI training. Information from your Drive is never used for advertising, never sent to advertising, analytics or session-replay providers, never sold, and never used to create, train or improve generalized AI or machine-learning models.
- People. Our team does not read your files unless you ask us to (for example, by requesting a proof or a reviewed quote), or it is needed for security or to comply with the law.
packOS's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The full terms are in our Privacy Policy, Section 6.1, and our Terms of Service.
04 Disconnecting
Disconnect a Google account in Vault at any time. That deletes the refresh token we hold and stops new imports through that connection. Files already imported stay in your Vault as your content, where you can delete them.
Disconnecting in Vault does not remove packOS's access on Google's side. To do that, open your Google Account's third-party connections, choose packOS and select Remove access.
05 For Google Workspace admins
Import files uses only drive.file, which most Workspace domains allow without any change. If your
domain restricts third-party apps, an administrator can allow packOS in the Google Admin console under
Security → Access and data control → API controls → Manage third-party app access, by adding packOS and
marking it Trusted.
06 OneDrive and Dropbox
Vault can also connect Microsoft OneDrive and Dropbox accounts in the same way. Each purpose is again a separate connection, and information from those accounts is handled under the same limits as Google Drive. The permissions each provider asks for are listed in our Privacy Policy, Section 6.1.
07 Questions
Write to privacy@packos.ai about your data, or security@packos.ai to report a security concern. How we protect files in general is on our security page.