Privacy Policy
Release-candidate versions: Android 1.0.14 (19) and iOS 1.0.14 (15)
These two versions are release candidates. This notice describes how they are built to work; it does not mean they are published or installed on your device, and details may change before release.
- Android 1.0.14 (19) and iOS 1.0.14 (15): this notice takes precedence over the introduction and sections 1 to 6 and 10 below wherever they mention Google AdMob, Google's consent screen (UMP), when Firebase starts collecting, native ads, or Google as the recipient of advertising data. In section 6, advertising data goes to Unity (LevelPlay, ironSource and Unity Ads) instead of Google; Firebase data still goes to Google.
- Earlier versions that contain Google AdMob and UMP (including Android 1.0.10 (14) and iOS 1.0.10 (10)): the sections below apply as written.
- Earlier LevelPlay candidates (such as Android 1.0.11 (15) and iOS 1.0.11 (11)): they asked for an age group, and ads and analytics started only after you chose 18 or older and allowed them.
In the candidate versions
- Ad services. Ads come from Unity LevelPlay (ironSource) with Unity Ads, and the Unity Ad Quality SDK included with LevelPlay checks ad quality. The candidate builds contain no Google Mobile Ads and no Google UMP. These providers may process advertising or installation identifiers, IP address and approximate region, device and app information, ad impressions and interactions, performance and diagnostic information, and your privacy choices, for advertising, measurement, ad quality checks and fraud prevention, including in the United States and other countries, under the Unity player privacy policy and ironSource privacy policy. Resetting your ad ID does not erase data a provider already holds.
- Your choices. Where consent is required (the EEA, the United Kingdom and Switzerland, including some related territories that cannot be told apart, or when the region cannot be determined), the app shows its own choice screen instead of Google's; elsewhere it starts with the defaults below and shows no first-launch screen. There is no age question: turning on child protection (under 18) in Settings turns off third-party ads and analytics and leaves only the developer's own app banners. You can choose separately: device access for ads, personalized ads, usage analytics and crash reports (one choice covering both Firebase services), and a do-not-sell-or-share signal. You can refuse everything and keep using the app, and you can change the choices in Settings at any time, including offline. The diagnostics switch in Settings can additionally turn off Firebase collection. On iOS, Apple's tracking prompt is separate from these choices.
- When ads are requested. Where consent is required, the app requests an ad only after you allow device access; elsewhere it requests ads without personalization unless you allow personalized ads. With child protection on it makes no ad request, and in every case it requests ads only if the developer has switched on ad delivery in the published build. Ads are a banner at the bottom of the Home tab, a banner at the bottom of the Tools tab and of the History tab (when it has items), an interstitial after an export once you leave the result screen, and an optional rewarded ad shown only for advanced results when you tap to watch an ad and save. Native ads are not shown. If the rewarded ad is not ready after a short wait, an introduction to another app by the developer may appear first, and the export proceeds without an ad.
- Your choices are passed on. Your personalization and do-not-sell-or-share choices are passed to the ad SDKs as consent or opt-out settings, whether you accept or decline. Declining personalization does not stop the ad SDKs from processing device data for ads you allowed device access to, and it does not promise that a contextual ad will be shown.
- Firebase. Firebase Analytics and Crashlytics start switched off and are then set by one rule, in this order. If child protection is on or you declined, nothing is collected in any region. Before the regional reconfirmation update described below, if you allowed usage analytics and crash reports, that saved permission applies in every region and keeps applying after you move or travel, including into the EEA, the United Kingdom or Switzerland, until you change it in Settings. Only with no saved choice does the region decide: collection is on by default where consent is not required, in the EEA, the United Kingdom and Switzerland it starts only after you allow usage analytics and crash reports, and if the region cannot be determined, nothing is collected. The region is decided on the device, from information such as the network and SIM country, the device language region and the time zone. Nothing is collected while the diagnostics switch is turned off, Crashlytics reports only from release builds, and finishing an ad step does not turn them on. The events in section 2-2 are sent only while collection is on. Turning the choice off stops later collection but does not delete data already sent. The retention period set for the Analytics property has not been verified.
- Introductions to other apps. In the banner area, in the Android exit dialog, and before an export when the rewarded ad is not ready, the app may show a card or dialog introducing another app by the developer. It is built from information and images stored in the app. Showing it makes no advertising-network request and uses no advertising identifier; services you separately allowed, such as Firebase, work as described above. If you tap it, your device opens the store page, or gwangy.com if that fails, which handles data under its own terms.
- Developer server. These versions do not call any server operated by the developer, including its regional-policy service. The iOS app may look up its own App Store listing from Apple to check for updates. Opening this policy, the terms or gwangy.com in a browser connects to the developer's website like any web visit.
- Requests. That SDK providers process data does not remove your ability to ask the developer. Send access, deletion or other requests about SDK data to gwangy.claw@gmail.com; the developer will answer or direct you to the provider's process.
Notice added November 1, 2026: this section adds version applicability. It does not change the effective date or grant any new permission.
Updated November 15, 2026: the candidate versions above were updated to Android 1.0.14 (19) and iOS 1.0.14 (15), and the choice, ad-request and Firebase descriptions now follow the regional defaults in those versions. It does not change the effective date.
VideoFit: analytics choices in the next update
Notice added November 16, 2026: this section describes the regional consent reconfirmation implemented for the next Android and iOS update of VideoFit. It takes precedence over the saved-permission descriptions above only in builds containing this change; earlier builds keep their previous behavior. This notice does not mean that the update is already installed on your device.
For Firebase Analytics and Crashlytics, permission given in a region where consent is not required is paused when you enter a region that requires consent (the EEA, the United Kingdom and Switzerland, including some related territories), or when the region cannot be determined. We ask for consent again and do not transmit under that earlier permission until you agree in the consent-required flow. Error reports recorded on the device during the pause are retained rather than deleted and may be sent when collection is allowed again. If you return to a region where consent is not required without changing your choice, your earlier choice applies again. This pause does not delete your choice or unsent crash reports and is not treated as a refusal.
Permission given in the consent-required flow remains valid in every region, including when the region cannot be determined. If you declined analytics or turned on child protection, nothing is collected in any region. With no saved choice, collection remains on by default where consent is not required and off until you agree where consent is required or the region cannot be determined. Existing permissions without a record of the region in which they were given are treated as permissions given where consent is not required, so we may ask again after the update.
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). Unity's SDK disclosure guidance also lists user or installation identifiers, purchase history or tendencies, other usage information, and device language, model, screen size and connection type. Collection depends on the platform, consent and SDK settings; collection of Android app usage times applies when Acquire Optimization is enabled. VideoFit itself has no accounts or in-app purchases, and the developer does not send account IDs or purchase records directly to Unity. Unity may also process the contents of a report you submit about an ad creative. The information is used for advertising, analytics and SDK functionality 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 follows the Google Analytics property setting and provider policies. The period currently configured for this property has not been verified; aggregated statistics that do not identify you may be retained separately.
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.
- You can additionally opt out of Firebase Analytics and Crashlytics using the diagnostics collection switch in the app's Settings. A Crashlytics change may take effect on the next app launch. This switch does not disable all collection by Google's or Unity's advertising SDKs.
- 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. Ad consent and export requirements are separate. Depending on your installed version and export option, completing a rewarded ad may be required.
- On iOS, Apple's App Tracking Transparency prompt is shown. If you do not allow it, the advertising identifier (IDFA) is not used for ads. Export requirements are described in section 4.
- 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.
Ad formats and placements vary by platform and installed version. Some versions show banner ads on the Tools and History screens and offer an export option that proceeds after a rewarded ad is completed. If the ad is unavailable or not completed, that export option may not proceed.
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.
- Voice-over recording (supported versions) — microphone permission is requested when you choose to record. Refusing it prevents voice-over recording. Recordings stay in app storage on your device and are mixed into your video; they are not sent to servers or advertising or analytics SDKs. The recording folder is excluded from automatic backup, and unused recordings are removed during cleanup such as finishing editing or opening another video.
- 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 does not keep your videos or account information on a separate server. Deleting the app removes the locally stored history and settings immediately. Crashlytics retention follows Google’s service policies. Firebase Analytics user- and event-level retention follows the property setting and provider policies; the currently configured period has not been verified. Rights over information Google and Unity process can be exercised through their privacy policies and the device settings in 3.
The data privacy icon in a Unity ad provides information about that ad's data processing and routes to privacy choices and deletion requests. You may also contact the developer below about SDK data. For provider data the developer cannot delete directly, we will direct you to the provider's process. Resetting an advertising identifier or deleting the app does not by itself delete data a provider already holds.