VideoFit Character Icon VideoFit
한국어 · English

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.

In the candidate versions

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:

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.

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

4. Where ads appear

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

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.

11. Contact

gwangy.claw@gmail.com

Effective date: October 7, 2026 · Factual clarification: October 30, 2026

Release-candidate notice added: November 1, 2026. The effective date is unchanged.