Cloud Import Privacy
Moving your life out of Google Drive, Dropbox or iCloud Drive should not create another readable copy. Here is exactly what happens for each supported transfer path.
1. Encryption happens in your browser
When you pick files from a connected provider, File-A-Cloud fetches them into your own browser session. If you choose Private protection, each file is scrambled with your PIN on your own device before it is uploaded to File-A-Cloud's storage. We never see the readable contents of your private files.
2. We never collect provider passwords
File-A-Cloud never asks for or stores a Google, Dropbox or Apple password. Supported providers show their own authorisation screen and issue a limited, revocable connection. The encrypted connection handle is kept server-side and can be cut off in one click.
3. One-way movement
Connected imports only read the items you choose. Nothing from your File-A-Cloud account — including files, tags or smart folders — is sent back to a provider. iCloud Drive has no public third-party OAuth interface, so its secure path uses Apple's own Files picker or a downloaded copy instead of collecting credentials.
4. Optional Shredding
If you choose the "Destroy originals" option, File-A-Cloud will permanently delete the supported source files and empty the provider's bin after they are safely stored in File-A-Cloud. This ensures no shadow copy remains in your old account.Warning: Source deletion uses the provider's own API and cannot be undone by File-A-Cloud. It is not available for iCloud picker imports.
Why can a provider request broad access?
Some provider permission systems cannot separately grant browsing and permanent deletion. To select from any folder and optionally remove originals, they may request broad file access. File-A-Cloud only acts on items you select, records every import and deletion result, and lets you disconnect immediately.
Privacy guarantee and necessary limits
File-A-Cloud does not scan private imported content for advertising, sell it, or grant another app access without your explicit action. Once encrypted and stored in File-A-Cloud, the readable file requires your unlocked vault. During the move, Google necessarily holds and sends its existing readable copy, and your device must briefly process readable bytes before browser-side encryption. A compromised device, browser extension or operating system can observe data while you use it; no app can truthfully promise otherwise.