Gyeolbit Privacy Policy

01Photos and editing data

• The app reads only the photo that you explicitly select through Android Photo Picker.
• Photo pixels, masks, adjustment values, and presets are processed on your device for editing.
• Photo pixels and editing data are not sent to a Gyeolbit Studio server. We do not operate an app server for Gyeolbit.
• Newly saved images do not copy original metadata such as location, capture device, or capture time.

02Data stored on your device

The app may store the following information locally on your device:

• Display theme and presets that you create locally
• A photo URI, source properties, editing commands, and masks used to restore an interrupted editing session
• Ad-frequency information, including the first-success exemption, last display time, displays per local date, and the time of a purchase-screen interaction
• PRO status verified by Google Play, verification time, product ID, app package name, and schema version

The ad-frequency store does not contain photos, photo URIs, accounts, advertising IDs, or purchase tokens. The app also does not persist raw purchase tokens, order IDs, payment methods, or Google Account information in its local storage.

03Google Mobile Ads and consent

After a free user successfully saves or shares a photo, the app may request an interstitial ad through the Google Mobile Ads SDK. The Google User Messaging Platform SDK is used for regional consent checks and privacy choices.

According to Google’s current Mobile Ads SDK disclosure, the SDK may automatically collect and share the following data with Google for advertising, analytics, and fraud prevention:

• IP address and the approximate location inferred from it
• App interactions such as launches, taps, and ad views
• Diagnostic information such as app and SDK performance, runtime, crashes, and energy usage
• App Set ID and other device- or account-related identifiers

The legacy Android advertising ID permission is removed from the app manifest. This does not mean that all other identifiers or network data processing by Google SDKs is disabled. Google states that data sent by the Mobile Ads SDK is encrypted in transit using TLS. Where required, a consent form is shown. You can revisit your choices through Ad privacy settings in the app. After Google Play verifies PRO entitlement, the user is excluded from ad SDK initialization, loading, and display.

04Google Play billing

PRO is a non-consumable, one-time in-app product sold through Google Play. Google Play handles payment methods, pricing, charges, and transaction processing. The app processes the product ID, purchase state, and purchase token in memory as needed to verify, acknowledge, and restore a purchase. Only PRO status, verification time, product ID, package name, and schema version are stored locally.

We do not operate an account or billing server and do not send raw purchase tokens to our own server. Google Play processing is governed by the Google Privacy Policy (opens in a new tab).

05Saving and sharing

• Saved results are written to a location you select or to Pictures/Gyeolbit through Android MediaStore.
• When you share a result, the app creates a temporary cache file and gives the Android system share sheet a read-only FileProvider URI.
• The result is sent only to the app that you choose in the system share sheet.
• We do not control how another app handles a file after you choose to share it.

06Permissions and security

• INTERNET and ACCESS_NETWORK_STATE: Google Play billing, consent checks, and advertising
• Billing permission merged by the Google Play Billing library
• AdServices, wake lock, and foreground-service support permissions merged by Google SDK dependencies
• Android Photo Picker: read one photo that you explicitly select
• MediaStore or the system document creator: save an edited result at your request
• FileProvider: temporarily grant read access to a file that you choose to share

The app does not request broad photo-library, location, contacts, or accounts permissions. Local app data is excluded from Android cloud backup and device transfer.

07Retention and deletion

• An editing recovery file is retained only while it may be needed to restore the current edit, and is cleared when you choose a new photo or finish the edit normally.
• Temporary sharing files are stored in app cache and may be removed by Android or during app cleanup.
• You can delete the local theme, presets, recovery data, ad-frequency data, and PRO entitlement cache by clearing the app’s data in Android settings or uninstalling the app.
• Images saved to your photo collection or another location may remain after uninstalling the app and must be deleted by you.
• Data processed by Google for advertising and billing is retained and deleted under the applicable Google service policies and account controls.

Gyeolbit has no developer-operated user account, so it does not provide a separate app-account deletion feature.

08Children

Gyeolbit is not designed primarily for children and is not listed on Google Play as an app directed to children or families. If the intended audience or distribution policy changes, we will review the advertising configuration, data practices, and this policy before making that change.

09Changes to this policy

If app features, included SDKs, or legal requirements change, we will update the effective date and contents of this policy. Material changes will be communicated through the app or its Google Play listing.