This page is specific to Cloud Video Offline Playback. Third-party services have their own privacy policies.
01About this policy
This policy applies to Cloud Video Offline Playback, also displayed as Cloud Video and previously listed on the App Store as Offline Cloud Video Player Max. It describes the iPhone and iPad player’s handling of information when you import, download, organize, or play your own media. The developer is Li Ying (莹 李).
02Media and information on your device
The app processes imported media, filenames, folder paths, file sizes, subtitles, thumbnails, playback positions, viewing history, download records, and settings to provide its player and library features. Downloaded files are stored in the app’s local library. The developer does not operate a server that receives your media library or cloud account passwords. Files and settings may be included in device backups that you enable.
03Google Drive
Connecting Google Drive is optional. Google handles sign-in in the system authentication browser. The app uses Google’s official file picker and requests only the drive.file permission to access files you explicitly choose, rather than requesting access to your entire Drive. The app reads the selected files’ identifiers, names, types, and sizes, and downloads their contents when you request a download. It also reads an account-specific Drive identifier so that selections from different Google accounts are not combined. The implemented Drive functions read and download files; they do not edit, move, or delete the source files in your Drive. The app stores its authorization refresh token, the account identifier, and its selected-file list in the device Keychain, and keeps access tokens in memory while needed. The app does not receive your Google password. Google Drive data is used for the visible file-selection, download, organization, and playback features. It is not sold, provided to advertising services, used for ad targeting, or used to train AI models. Our use of Google user data follows the Google API Services User Data Policy, including applicable Limited Use requirements.
04Other cloud services
You may optionally connect Dropbox, OneDrive, or MEGA to browse and download your own files. The relevant provider receives requests needed to authenticate and transfer those files. Dropbox and OneDrive use their provider sign-in flows. MEGA credentials entered in the app are passed to the official MEGA SDK to sign in; the app does not persist the entered password. Provider authorization or session information is stored locally using the provider SDK or device Keychain. These providers also apply their own privacy policies.
05Photos, Files, and local transfers
Photo and file import processes items you choose through the system picker or explicitly allow the app to access. Wi-Fi transfer connects a browser on your local network to the app using a temporary transfer password. USB file sharing and other local imports add files to the same local library. These transfers do not upload your media to a developer-operated server.
06Advertising and purchases
The app uses Google AdMob and Google’s consent-management service for advertising. Google may process device identifiers, IP addresses, app interactions, and other advertising or diagnostic information according to your consent choices, device settings, and Google’s policies. Your selected Drive files and media contents are not supplied to the advertising SDK as advertising data. See Google’s Privacy Policy. Where available, advertising privacy choices can be reviewed in the app’s settings. Apple handles in-app purchases and restores. The app processes StoreKit purchase information to determine whether the advertising-removal entitlement is active. The developer does not receive your payment-card details.
07Firebase analytics and crash diagnostics
Cloud Video uses Google Firebase Analytics and Crashlytics to understand feature usage and diagnose reliability problems. Usage analytics records app launches, sessions, fixed page categories, playback and download results, media format categories, and cloud provider categories. Crashlytics receives crash stacks, app version, operating system and device information, and sanitized nonfatal error categories and codes. Firebase may process installation or app-instance identifiers and connection information such as IP addresses to deliver these services. Analytics may infer your approximate country or region from connection information; this integration does not request GPS or device location access. We do not set an account-based analytics user ID. Custom events and nonfatal reports do not include video names or contents, folder names, cloud file identifiers or URLs, search text, account names, passwords, or authorization tokens. Unexpected crash stacks or exception messages can contain runtime details. Analytics uses the SDK without IDFA collection; IDFV collection, advertising personalization signals and advertising-data consent are disabled for this analytics integration. This does not replace the separate AdMob privacy choices. The app does not use Firebase to upload your media library.
08Your controls and retention
You can sign out of a cloud provider in the app and manage that provider’s authorizations in your provider account. Signing out of Google Drive clears this app’s saved Google authorization and selected-file list on this device; it does not delete files from Google Drive or remove media you already downloaded. Revoking access through Google prevents further authorized requests. You can manage downloaded media and local history using the app’s library and settings. Removing the app removes its app-container files according to iOS behavior; cloud-provider grants and Keychain records should also be managed through the app’s sign-out controls and the relevant provider. Usage analytics and crash reporting are enabled by default and can be switched off independently in Settings → App diagnostics. Analytics collection stops when disabled; changes to crash collection fully apply after restarting the app, and locally pending crash reports are discarded when crash reporting is disabled. Turning a switch off does not erase reports already received by Firebase. Firebase Analytics retention follows the property’s data-retention settings; Crashlytics keeps crash traces and associated identifiers for 90 days before starting their removal from live and backup systems. Google processes this information under its Firebase privacy and security terms. For deletion questions about previously submitted diagnostic data, contact us; do not include media or passwords.
09Security and support
Cloud authorization and API requests use HTTPS. Saved Google and MEGA credentials or session records use the device Keychain. Keep your device and cloud accounts secure. If you choose to send feedback, your email provider receives the message you send; the app includes basic app and device diagnostics to help reproduce bugs and lets you review the message before sending. You choose whether to send it. For privacy questions, contact duckling-feedback@outlook.com.
010Changes
Changes to the app’s data practices will be reflected in an updated policy and effective date. New permissions will be requested when the corresponding feature needs them.
Google Privacy Policy / Google 隐私政策 · Firebase Privacy and Security / Firebase 隐私与安全
View all privacy policies