GifPingGifPing

Privacy Policy

Last updated: October 2026

Introduction

GifPing is an app by PingApps Lab that turns a video you already have into an animated GIF. Conversion happens on your device. This policy explains what is stored locally, what may be sent over the network, the permissions GifPing requests, and how you can delete your data.

Your video stays on your device

All conversion — reading the video, trimming the clip, and encoding the GIF — happens entirely on your device, and the app never uploads your videos or your GIFs to PingApps Lab's servers or to any other server of ours: there is no cloud processing and no server round-trip on our side. Copies can still exist off your device in three ways, none of them an upload by GifPing:

  • Android auto backup — the app opts into Android's automatic backup (it is enabled in the manifest with no backup exclusions), so the system may copy the app's private files — including the GIFs in your History — to your device backup service (usually Google Drive), unless you turn backup off for GifPing.
  • Saving to your gallery or Photos — a GIF you save becomes an ordinary file, and if your gallery or Photos has cloud sync or backup switched on, that file can sync to that cloud. That sync is your setting, not something GifPing performs.
  • Sharing — when you share a GIF (or share a video into GifPing), the file goes to the app you share it with, under that app's own rules.

How GifPing accesses your video

On Android, you choose a video with the system video picker, which hands GifPing only the file you selected. GifPing requests no storage or photo-library permission to read your videos. On iPhone and iPad, you choose a video through the system photo picker, and GifPing can also receive a video shared to it from another app's share sheet via its share extension.

Saving your GIF

When you save a finished GIF, GifPing writes it to your device. On Android it lands in Pictures/GifPing in your phone's library; on iPhone and iPad it is added to your Photos library using add-only access, so GifPing can add the GIF but cannot read your existing photos. A saved GIF is an ordinary file that stays in your gallery until you delete it there.

No account required

GifPing requires no account, sign-in, or registration of any kind. There is no user profile and no login, and PingApps Lab does not link your data to an identity — we hold no account that could link it to. One qualification: the ad and analytics SDKs named below collect device-level identifiers and interaction data from your device, and Apple's App Privacy label marks some of that data as linked to you, because those SDKs collect it — not because it is tied to a GifPing profile. Your history, settings, and GIFs are stored locally on your device.

Permissions and app access

On Android, GifPing declares the following permissions:

  • Notifications — the manifest declares POST_NOTIFICATIONS, but GifPing posts no notifications: GIF progress is shown only inside the app while a conversion runs.
  • Storage write (legacy, Android 9 and below only) — to save a GIF into Pictures/GifPing on devices before Android 10. On Android 10 and above the system scoped-storage insert needs no permission, so this is never requested there.
  • Foreground service — declared for WorkManager's internal SystemForegroundService (dataSync type); GifPing's own GIF generation runs in an app coroutine and does not use a foreground service.

GifPing does not request access to your contacts, microphone, location, or your existing photos and videos. On iPhone and iPad, GifPing asks for add-only Photos access only when you save a GIF, and it may show the system tracking permission (ATT) prompt once for ads.

Advertising (free users only)

Free users see a single small banner ad, served by Google's Google Mobile Ads (AdMob) SDK with Meta (Facebook) Audience Network enabled as a mediated ad network through the AdMob mediation adapter — both ad network SDKs are present in the app on Android and on iPhone and iPad. No other ad network is integrated. There is no interstitial, rewarded, native, or app-open ad. Subscribers never see ads.

Requesting and measuring an ad sends data off your device to those ad networks as third parties. The ad SDKs may collect a device or advertising identifier (the advertising ID on Android; the IDFA on iPhone and iPad), your IP address (from which approximate location is derived), ad and product-interaction data — ad requests, impressions, and clicks — and diagnostic data, for advertising, analytics, and fraud prevention. PingApps Lab itself never logs or collects any ad identifier or ad-unit ID.

On iPhone and iPad, tracking is governed by Apple's App Tracking Transparency (ATT): after you complete Google's consent form, the app asks for permission to track you, and identifiers are used for tracking only if you allow it.

Analytics and crash reporting

GifPing includes Firebase Crashlytics (crash reports) and Firebase Analytics (usage analytics) on both Android and iPhone and iPad. Both are enabled in release builds and there is no in-app setting to turn them off.

They are strictly content-free: they never include your video, the GIF you create, filenames, or file paths. Crash reports carry technical information such as a stack trace, device model, OS version, and app version. Analytics record bounded events and enum values — for example that a GIF run started or finished — with no media content.

Purchases

GifPing has one optional purchase: a single auto-renewing monthly subscription (product id gifping_pro_monthly) that removes the banner ad. It is billed monthly by Google Play on Android or the App Store on iPhone and iPad, at the price the store lists, and it renews automatically until you cancel it. You manage and cancel the subscription in your store account's subscription settings — not in the app.

Purchases are processed entirely by Google Play or the App Store under each store's own policies. GifPing never collects your payment details (card number, billing address); the store's own checkout collects that directly, and GifPing's code never has access to it. The purchase token the store returns is used only to confirm and restore your subscription. PingApps Lab has no payments database of its own. The Android and iOS subscriptions are separate purchases.

Data and deletion

All of GifPing's data — your GIF history and app settings — is stored locally on your device. PingApps Lab does not hold a copy of it, so there is no account to close and no server-side data to request the deletion of.

You can delete individual GIFs from the app's History at any time. Uninstalling GifPing removes all of its on-device data. GIFs you have already saved to your gallery or Photos are ordinary files and remain until you delete them yourself.

Changes to this policy

If we make material changes to this privacy policy, we will update this page. We encourage you to review this policy periodically. Continued use of GifPing after a change is posted constitutes your acceptance of the updated policy.

Contact

Questions about this policy or how GifPing handles your data: [email protected]