- After you sign up, allow Pics.io to get access to your Google Drive. Apart from this consent, Pics.io never requires any other information about your Google account, such as login names or passwords. Pics.io doesn’t know password to your Google Drive, and there’s no chance it can get access to it.
- Choose a folder inside your Google Drive that you want to connect with Pics.io. If you already have assets in this folder, they will become available in Pics.io after sync. The service will work only with the content of this folder and never touch other files and folders in your Google Drive. Alternatively, you can let Pics.io create a new Picsio folder in your Google Drive.
Google Drive doesn't support permission on the folder level to third party applications. That is why Pics.io needs to ask for access to the entire Google Drive of the user. However, Pics.io activity is only limited to one single working folder you choose to connect with Pics.io app.
Pics.io doesn’t use usual Google Drive sharing mechanism. Access to your working folder is performed via cryptographic keys provided by Google Drive API.
Any recommendations for teams?
If you are planning to use Pics.io as a team, it is highly recommended to use Team Drive with Pics.io (you can read more about it here). The best scenario is to create a separate Team Drive and provide Pics.io with access to that. In this case you won’t have to give access to the rest of your Google Drive. Read more about Pics.io integration with Team Drive here.
Any other security measures available?
Pics.io doesn’t store your assets. Google Drive does. So common-sense security measures in Google apply here as well.
Pics.io dev team does not have access to your digital repository. We can only get access to your assets at your consent for support purposes.
For greater security, access to Pics.io production servers is limited to very few members of our dev team.
You may also be interested to learn more about the following: