Cloudply logo
Cloudply: Media Transfer
Privacy-focused transfers between cloud providers

Privacy Policy

Effective date: August 15, 2026. This policy explains what data Cloudply ("the app"), developed by Abdul Khaliq Mangat, handles, where it is stored, and how you can control it. A printable copy is available as a PDF download.

Short version: Cloudply has no servers that store your media. Photos and videos move directly between your provider accounts while the app runs on your device. Temporary files exist only during an active transfer and are deleted when it finishes. We do not sell data, we do not show ads, and no human ever views your media.

1. Information we handle

1.1 Provider accounts you connect

You choose to connect cloud provider accounts (Google Photos, Dropbox, Box, OneDrive, MEGA, or local storage). Cloudply stores basic account information — such as the account name, provider type, and storage usage reported by the provider — on your device so the app can resume and manage transfers.

1.2 OAuth tokens

When you sign in, your provider issues an OAuth token that lets the app read and write the media you authorize. Tokens are stored in the secure credential storage of your operating system (for example, Android Keystore or iOS Keychain). They are never written to plain files, never uploaded, and never shared with anyone.

1.3 Media metadata

To build transfer plans and progress reports, Cloudply stores metadata about your media — such as filenames, file sizes, modification dates, and provider item identifiers — in a local database on your device. This database never leaves your device.

1.4 Temporary media files

During an active transfer, media may be staged temporarily on your device so it can be moved reliably between providers. Temporary files are used only while a transfer is active and are removed as soon as the transfer completes. No media binary is persisted beyond an active transfer lifecycle.

1.5 Transfer logs and diagnostics

The app keeps local logs of transfer activity (for example, which items succeeded or were skipped, and error codes) so that interrupted transfers can resume and you can review what happened. Crash information generated by the operating system may be collected by the app store platforms (Google Play, Apple App Store) according to their own policies.

2. How we use your data

3. What we do not do

4. How each provider's data is used

4.1 Google Photos

Cloudply uses the official Google Photos picker, which is limited to the items you select. The app never requests full-library access. Selected items are copied to the destination you choose. Storage figures shown in the app for Google Photos reflect selected items only, not your full Google Photos quota.

4.2 Dropbox, Box, OneDrive, MEGA

For these providers, Cloudply requests access to the folders you authorize, reads the metadata of media in those folders, and copies media you select. No content is used for any purpose other than performing your transfers.

5. Data retention and cleanup

6. Removing your account and data

You can disconnect a provider and delete its local data at any time from Settings inside the app. Deleting an account removes the saved tokens, local metadata, and logs for that account; it does not delete files from the provider itself, because Cloudply never modifies or deletes your source files unless you explicitly confirm a delete action.

To request full deletion of data associated with your email address, or if you have questions about this policy, contact privacy@abdulkhaliqmangat.com. See the Delete Account page for the full procedure.

7. Children's privacy

Cloudply is not directed at children under 13, and we do not knowingly collect personal information from children.

8. Security

Tokens are stored in OS-level secure storage, transfers run on your device, and the app contains no server component that could be breached to access your media. See the Security page for details.

9. Changes to this policy

If this policy changes, the revised version will be posted at this URL with a new effective date. Significant changes will be noted in app release notes.

10. Contact