A few days ago the SafeInCloud Pro application, I request permission to access my Google Drive account. I had synchronized the backup with d
A few days ago the SafeInCloud Pro application, I request permission to
access my Google Drive account. I had synchronized the backup with
drive. The thing is that the permissions are total, read, write and
delete any file from my account.
Why do you need these permits? if they only use only one file.
Google drive permissions are definitely way too widespread. Other apps specify that they have permissions to files/folders they create. Upvote this 1000x. Do these suggestions go anywhere? Can we get the developer to at least acknowledge and provide an opinion on this huge security concern?
I agree. I prefer the previous method that did not require any Google permissions. I can't find any documentation that explains why the change is an improvement over the prior method. I have revoked permissions until this is clarified. The ability to store my encrypted password file in a 3rd party (Google) cloud is the primary reason I use Safe In Cloud. I do not want to provide full read/write/delete permissions to all of Google Drive. The app should only need access to the local file for maximum end-user security.