Privacy Policy

Last updated: October 19, 2026

This Privacy Policy explains how Bokeria ("we", "us", or "our") handles information when you use the HEIC JPG Converter mobile application (the "App") on Android or iOS. The App converts HEIC/HEIF images on your device into JPG files and other supported output formats where available. We do not upload your selected photos or converted images to our servers.

1. Information the App Accesses or Processes

Photos, images, and media metadata

The App requests access to photos and media files so that it can find or let you select HEIC or HEIF images on your device, show selected images in the App, and convert selected images to JPG files or other supported output formats where available.

Depending on your Android version and permission choices, the App may request or use permissions such as READ_MEDIA_IMAGES, READ_MEDIA_VISUAL_USER_SELECTED, READ_EXTERNAL_STORAGE, and ACCESS_MEDIA_LOCATION. These permissions are used for the App's image selection and conversion features.

On iOS, the App may use the system photo picker to let you choose images and may request photo library permission when saving converted images to your photo library. iOS photo access is controlled by Apple system settings and may be limited to selected photos.

Image browsing and conversion are performed locally on your device. The App may read file information such as image URI, file size, width, height, folder name, and image metadata needed to display, sort, validate, and convert HEIC images.

EXIF metadata and location metadata

When converting an image, the App may copy selected EXIF metadata from the original HEIC/HEIF image to the converted JPG file. This can include date and time, camera make/model, orientation, exposure information, and GPS location metadata if that metadata exists in the source image and your device grants access to original media location metadata.

Converted files are saved to your device's Pictures folder, photo library, or another location you choose depending on your platform and App version. If you share a converted file with another app or person, the copied metadata may be included in that shared file. Please remove metadata before sharing if you do not want it to be included.

Local app settings

The App stores a small amount of local settings data on your device, such as app preferences, review prompt status, ad display or rewarded-ad state, and feature unlock status. This information is stored locally and is used to operate App features.

Android purchases and purchase restoration

Android versions that offer paid passes use Google Play Billing for a prepaid 7-day pass and a non-consumable lifetime pass. Both passes remove ads and the photo selection limit while active. The 7-day pass does not renew automatically. These Android purchases do not grant access on iOS.

Google Play processes payments under Google's terms and privacy policy. The App does not receive or store your credit card number, bank account details, or other payment credentials. The App receives product IDs, purchase tokens, purchase status, and acknowledgement status from Google Play to confirm, acknowledge, and restore eligible purchases, and to apply or remove paid features. This verification is performed through Google Play Billing in the App, without a separate purchase verification server operated by us.

The App stores the active pass type, the last successful purchase check, and device timing information locally to manage access, including limited offline access. Purchase tokens are used during purchase processing and are not saved in this local access cache. The cache is excluded from Android cloud backup and device transfer; after reinstalling, eligible purchases can be restored using the same Google Play account.

Diagnostics and analytics

The Android app uses Firebase Analytics and Firebase Crashlytics. These services may collect app usage, device, app version, crash, performance, and diagnostic information to help us understand reliability issues and improve the App. We do not intentionally include your photos or converted images in crash reports.

On Android, Firebase Analytics may also collect in-app purchase and subscription events, including product ID, product name, price, and currency, depending on the Google Play integration and service settings. These events are used to understand purchase activity and improve the App. Removing ads with a paid pass does not by itself disable analytics or crash diagnostics. The Android app does not provide separate in-app switches for Firebase Analytics and Crashlytics.

In the current iOS release 1.0.5 (build 18), Firebase Analytics and Firebase Crashlytics are not initialized. Google AdMob still processes advertising and diagnostic data as described below. This does not mean that the iOS app sends no data.

Advertising data

The App uses Google AdMob to show banner ads and rewarded interstitial ads. Google may process information such as ad requests, ad impressions, ad clicks, device information, IP addresses used to estimate approximate location, and identifiers as described in Google's policies. This advertising use of approximate location is separate from reading GPS metadata in selected photos.

The Android production release 1.2.15 (version code 36) includes the Advertising ID permission (com.google.android.gms.permission.AD_ID) in its merged manifest. Google Mobile Ads may process the advertising ID when available and permitted. Not calling the Advertising ID API directly does not prevent SDK access. On iOS, the App may request permission through Apple's App Tracking Transparency framework before Google Mobile Ads starts. You can allow or deny this permission in iOS system settings.

On Android versions with Google UMP integration, the App refreshes advertising consent information, shows a consent form when required, and checks whether ads may be requested before initializing ads. Advertising consent does not itself disable Firebase Analytics or Crashlytics.

Ad request settings may vary by platform and App version. Where configured, ad requests may include child-directed treatment, under-age-of-consent treatment, ad personalization, publisher first-party identifier, or maximum ad content rating settings.

Information you send to us

If you contact us by email or through another support channel, we may process your email address, message content, and any information you choose to provide so that we can respond to your request.

2. How We Use Information

We use information for the following purposes:

3. When Information Is Shared

We do not sell your photos, converted images, or personal information. We do not upload selected HEIC/HEIF files or converted JPG files to our servers.

Information may be shared or processed in these situations:

4. Third-Party Services

The App uses third-party services that may process information under their own terms and privacy policies:

5. Data Retention

As verified on October 19, 2026, the Android app’s Firebase-linked Google Analytics property has its event-data retention setting at 2 months and its user-data retention setting at 14 months. Google applies the user-data period to key events. The user-data retention period resets on new user activity. These settings do not affect most standard reports based on aggregated data and do not determine retention for other services. See Google Analytics data retention for the scope of these controls.

Android may back up or transfer eligible local settings according to your device and Google account settings. The purchase access cache and temporary incoming-share files are excluded by the current Android backup rules. Clearing app data does not delete copies already held by a backup or another service.

6. Your Choices and Controls

If you deny photo access, the App may not be able to find and convert HEIC images from your device library, or it may only be able to use images that you specifically select.

7. Security

We use reasonable technical and organizational measures designed to protect information processed through the App. However, no electronic transmission or storage method is completely secure. Please take care when sharing converted images, especially if they may contain EXIF or location metadata.

8. Children's Privacy

We do not knowingly collect contact information from children. The App does not universally mark ad requests as child-directed or as under the age of consent. Ad content rating settings differ by platform and version; a rating limit is not a statement that all users are children. If you believe a child has provided us personal information through a support request, please contact us so that we can take appropriate action.

9. International Processing

Third-party services used by the App, including Google services, may process information on servers located in countries other than your country of residence. These services process information according to their applicable terms, policies, and legal safeguards.

10. Changes to This Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last updated" date above. Your continued use of the App after an update means that you acknowledge the updated Privacy Policy.

11. Contact Us

If you have questions or requests about this Privacy Policy, please contact us at appsupport@bokeriastudio.com.