1. Scope and app identity
This policy applies to the Android application
Video Compressor (package
com.haiwaidao.videocompressor), including its
compression, trimming, audio extraction, batch processing, history,
sharing, and settings features.
In this policy, “we” means the developer of Video Compressor. We do not operate a user account system or a developer-hosted service for storing your media.
2. Media processing and local data
When you choose a video or audio file, Android’s Photo Picker or system document picker gives the app access to the item you selected. The app reads only what is needed to display information and perform the requested operation, such as the file name, size, duration, dimensions, rotation, codec, frame rate, audio tracks, and a preview thumbnail.
Compression and FFmpeg processing run on the device. The app may copy the selected item into an app-private cache while a task is running. Temporary task files are removed after completion or failure, and the cache can also be cleared from Settings.
Completed files are saved locally, normally in the device’s
Movies/VideoCompressor folder or the app-specific
external files area. The app does not upload these files to us.
Sharing or opening an output file is a user-initiated Android action;
the selected target app then handles the copy or transfer.
Local history and preferences
To show progress and history, the app stores a local record containing items such as the selected URI, display name, file sizes, duration, output dimensions, task status, compression options, timestamps, and error details. It also stores app preferences and the local Pro entitlement cache on the device. These records are not sent to a developer server by the app.
You can delete individual history entries, clear history, clear the compression cache, or remove app data through Android settings. Files already exported to the public Movies folder may remain until you delete them yourself. Android backup or device-transfer features may copy app-private data according to your device and Google account settings.
| Information | Purpose | Where it is handled |
|---|---|---|
| Selected media and technical metadata | Read, preview, trim, extract audio, and compress the item you selected | On your device |
| Temporary working files | Provide stable input and output files for FFmpeg processing | App-private cache; cleaned up after tasks |
| Compression history and preferences | Display history, progress, settings, and cached Pro state | Local app database and preferences |
3. Firebase Analytics and Crashlytics
The app uses Google Firebase Analytics to understand feature usage and improve reliability. The events sent by the app include:
- video selection and media-analysis failures;
- compression start, completion, cancellation, and failure;
- duration and resolution ranges rather than exact media values;
- compression mode, codec, audio mode, and reduction percentage; and
- the type of an exception when a compression failure is reported.
The app telemetry code does not include the media file itself, its file name, content URI, filesystem path, media bytes, or custom FFmpeg command in these events. Firebase may also automatically process service data such as app and device identifiers, app version, device model, operating-system version, session information, IP address or an approximate region, and diagnostic information.
Firebase Crashlytics receives crash reports and non-fatal exceptions so we can diagnose failures. These reports may contain stack traces, timestamps, app version, operating-system and device information, installation or session identifiers, and other diagnostic context supplied by the SDK. The app does not deliberately add media names, URIs, paths, or purchase tokens to Crashlytics.
Firebase processes this information on our behalf under Google’s terms and privacy practices. See Privacy and Security in Firebase . Firebase’s service documentation describes retention periods that vary by service; Crashlytics crash traces and associated identifiers are generally retained for 90 days before deletion begins, subject to the project’s current settings and Google’s policies.
4. Google Mobile Ads
Free builds may use Google Mobile Ads to display banner, native, or interstitial advertising. An ad request is made only where an advertising component is enabled in that build. Pro entitlement is intended to remove in-app advertising after Google Play confirms the purchase.
When Google Mobile Ads is used, Google may automatically collect and share information such as the device IP address, ad or product interactions, diagnostic information, Android Advertising ID, app-set or other device/account identifiers, and an approximate location inferred from the IP address. This information is used for advertising, analytics, and fraud prevention. Our app does not place the selected media, file names, or media contents in an ad request.
Ad personalization and consent choices are also affected by Google and Android settings. For details, see Google’s Google Play data disclosure for Mobile Ads and Google Privacy Policy .
5. Google Play Billing
The app offers a one-time, non-consumable Pro product with the
product ID pro_lifetime. Google Play handles payment,
billing credentials, tax, and order processing. We do not receive or
store your credit-card number, bank details, or Google Play password.
The app uses the Google Play Billing Library to query product details, show the purchase flow, acknowledge a completed purchase, and restore purchases on request. Google Play may return a product ID, purchase state, order-related information, and a purchase token to the app for these purposes. The current app does not send purchase tokens to a developer-operated backend.
Purchases are subject to Google Play’s terms and privacy practices. See Google Play Billing and Google Privacy Policy .
6. Permissions and notifications
The app does not request contacts, location, camera, microphone, or broad storage permissions. Android grants access to the media item you choose through the Photo Picker or document picker.
On supported Android versions, the app may request notification permission to show compression progress. A foreground service and a wake lock keep an active compression task running when you leave the app; they do not grant access to your media beyond the item you selected.
7. Retention, deletion, and your choices
Local media, exported files, history, and preferences remain on your device until you delete them, clear app data, uninstall the app, or remove exported files yourself. Temporary compression files are designed to be cleaned up after a task and can be cleared from Settings.
You can control notification permission, Android Advertising ID settings, ad personalization, Google Play purchases, and device backup through Android or Google settings. You may also decline to select media or stop using any feature.
Depending on your location, privacy law may give you rights to access, delete, correct, or object to certain personal data handled by service providers. Because the app has no developer-hosted media account, most media and history data can be removed directly on your device. For questions about data processed for this app by Firebase, Mobile Ads, or Google Play, contact us first; those providers may also have their own privacy request channels.
8. Children’s privacy
Video Compressor is not knowingly directed at children under 13. We do not knowingly collect personal information from children through a developer-operated account or media server. If you believe a child has provided personal information in connection with the app, please contact us so we can review the request.
9. Security and international processing
Local files are protected by Android’s storage and application boundaries. Data sent to Firebase, Google Mobile Ads, or Google Play is transmitted using the protections provided by those services. No method of storage or transmission is completely risk-free.
Google’s services may process information in countries other than the one where you live. Their applicable privacy notices explain their safeguards, retention, and international processing.
10. Changes and contact
We may update this policy when the app’s data practices or third-party integrations change. The effective date at the top of this page shows which version you are reading. Material changes will be reflected in a new dated version.
For privacy questions or requests, please open an issue in the Video Compressor repository . Do not include private videos, purchase credentials, or other sensitive information in a public issue.