VideoFitPrivacy Policy
Your videos are processed on your device. VideoFit has no sign-up or login, and never uploads your videos to any server, including the developer's. To stay free, VideoFit uses Google's advertising service (AdMob) and its mediation bidding partner Unity Ads, and Google and Unity process the information below in order to show ads. VideoFit also uses Firebase Crashlytics to diagnose crashes and Firebase Analytics for usage statistics.
1. Information the developer collects
None. The app never asks for your name, email, phone number or contacts, and does not communicate with the developer's servers. The content of your videos or photos, file names and location are never sent to the developer. If the app crashes, however, the error information in 2-1 below is sent to Google's Firebase Crashlytics and used by the developer to fix the error.
2. Information Google processes for ads
The Google Mobile Ads SDK and the User Messaging Platform (consent) SDK included in the app collect the following and send it to Google over TLS:
- IP address — may be used to estimate your approximate location. Precise location (GPS) is not collected.
- Device identifiers — the Android advertising ID and app set ID, the iOS advertising identifier (IDFA, only if you allow it as described in 3), or app- or developer-scoped identifiers.
- App usage — app launches and ad interactions such as impressions and taps.
- Diagnostics — app and SDK performance (launch time, hang rate, energy use) and, on iOS, crash logs not linked to you.
This is used to deliver ads, measure ad performance (analytics) and prevent fraud. Videos, photos and file names are never passed to the ad SDK. Google handles it under How Google uses information from sites or apps that use our services and the Google Privacy Policy.
Unity Ads — included as an AdMob mediation (bidding) partner. When an ad is served through Unity, Unity Technologies may process the same kinds of information (advertising identifiers, approximate location, ad interactions, device and diagnostic information) under the Unity Privacy Policy.
2-1. Crash diagnostics — Firebase Crashlytics (Google) — when the app crashes, the stack trace, device state, device model, OS and app version, and an installation identifier are sent to Google and used only to find and fix the cause. The content of your videos or photos and file names are not included. Privacy and Security in Firebase
2-2. Usage analytics — Firebase Analytics (Google) — an app instance ID, device model, OS, app version, language and an approximate region estimated from your IP address are sent to Google, together with the custom events below, to understand feature usage and improve quality. No user ID is used.
- Events — app open, video selected, tool selected (trim, compress, ratio and so on), export started, completed or failed, share tapped.
- Values sent with them — a resolution category (e.g. 1080p), a duration range (e.g. under 1 minute), a file size range, the tool type and, on failure, an internal error code. Only ranges are sent, never exact lengths or sizes.
- Never sent — file names, file paths, the content of videos or photos.
On iOS, if you allow tracking, the advertising identifier (IDFA) may also be processed. Retention: up to 14 months according to the Google Analytics retention setting; aggregated statistics that do not identify you may remain.
3. Consent and tracking
- Firebase Crashlytics and Firebase Analytics are off by default and are turned on only after the ad consent step (UMP) has finished. Analytics starts with all storage and ad signals denied (Google consent mode v2: analytics_storage, ad_storage, ad_user_data, ad_personalization), and a signal is turned on only according to the choice you make on the consent screen. In regions that require consent (EEA, UK and others), no analytics information is stored unless you consent. In regions where no consent screen is required (such as South Korea), it is turned on once the consent status check completes.
- In regions where the law requires consent (for example the European Economic Area and the UK), the app shows Google's consent screen on first launch. You can use every editing feature whether or not you consent.
- On iOS, Apple's App Tracking Transparency prompt is shown. If you do not allow it, the advertising identifier (IDFA) is not sent, and every feature works the same.
- To change your choice, tap "Manage ad privacy choices" in the app's Settings (shown only in regions where Google determines a privacy options screen is required). You can manage iOS tracking under Settings → Privacy & Security → Tracking, and reset or delete the Android advertising ID under Settings → Privacy → Ads.
4. Where ads appear
- Native ads — ad cards on the home screen and the export-complete screen.
- Interstitial ads — after an export finishes, with frequency and time caps.
There are no rewarded, banner or app-open ads.
5. How videos are handled and what stays on your device
- Choosing a video — the app receives only the videos you pick, through the system photo picker (Photo Picker on Android, PHPicker on iOS). It does not read your whole photo library or storage.
- Editing and conversion — all processing (trim, compress, resize and so on) happens on your device and videos are never uploaded. Temporary files created during processing are kept in the app's temporary storage and cleaned up.
- Saving — a converted video is only added to your gallery (Android) or Photos library (iOS) when you choose to save. Existing items are neither read nor deleted.
- Sharing — tapping share opens the system share sheet and you choose the receiving app. The app does not send it anywhere itself.
- History — the recent-conversions list (for example a file name and the size before and after) is stored on your device only and never sent to the developer. No copy of the original video is kept as history.
- Settings such as language and theme, and when the app last asked you to rate it, are also stored only on your device.
These are removed when you delete the app. Result videos you saved to your gallery or Photos library are yours and remain after the app is deleted. Values the ad SDK keeps on the device are managed by Google.
6. Third parties
Apart from the information in 2 being sent to Google and Unity Technologies to provide ads, the crash information in 2-1 being sent to Google through Firebase Crashlytics, and the usage information in 2-2 being sent to Google through Firebase Analytics, the developer shares nothing with third parties.
7. In-app purchases
None.
8. Rating prompts
The Android version may show the Google Play in-app review and the iOS version the App Store review prompt. Ratings and reviews are handled entirely by those stores; VideoFit does not receive them.
9. Children
VideoFit is not designed for children under 14 as its primary users and has no intent to knowingly collect children's personal information. If we learn of such a case, we take reasonable steps under applicable law and provider procedures.
10. Your rights
The developer keeps no personal information about you, so there is nothing to access, correct or delete. Deleting the app removes the locally stored history and settings immediately. Crashlytics crash reports are kept by Google for 90 days, and Firebase Analytics user- and event-level data for at most 14 months, and then deleted. Rights over information Google and Unity process can be exercised through their privacy policies and the device settings in 3.