[Privacy policy] This policy covers Foldmelo (폴드멜로, formerly Bankshot Studio / 뱅크샷 스튜디오), provided by OrbickK (Google Play developer name: Orbickk_Lab). The effective and last-updated date is 2026-10-20. The Android package remains com.orbickk.bankshot_studio; the rename does not change the app package or purchase product.

[Version scope] Closed-test version 0.6.2 verifies Google Play receipt signatures on the device. RevenueCat-enabled versions 0.6.3 and later send the purchase information and anonymous app identifier described below to RevenueCat for purchase verification, restoration, and Remove Ads access. Previously installed versions retain their behavior until updated. Test-ad builds identify their use of Google test ads in Settings. Live-ad builds request real ads and provide Google consent flows where required. Updating this policy does not itself launch the app publicly or change the ads in an installed test build. Purchases are disabled in earlier closed-test versions through 0.6.1.

[Accounts and permissions] You do not need a game account or need to enter a name, email address, or phone number. The game does not request GPS location, contacts, photos, camera, or microphone access. Advertising SDK data and support messages you choose to send are described below.

[On-device information] Board progress, scores, stars, collections, badges, selected palette and settings, help usage, and per-stage records such as attempts, shots, and play time are stored in app storage. Game code does not send these records to a developer server or public leaderboard. We do not use a separate developer behavioral analytics or crash-reporting SDK.

[Saves and backup] Local records support resuming play and displaying personal records. Depending on your Android settings and device, operating-system backup or device transfer may restore game records and SDK settings. There is no game-account progress synchronization. Verified Remove Ads status is stored with game records; the RevenueCat SDK caches an anonymous app identifier and purchase access information on the device. The app rechecks purchase access on launch, reconnection, and restoration. Clearing app data or uninstalling can erase local records; operating-system backups follow separate retention settings.

[Advertising] The game uses Google AdMob rewarded and interstitial ads. In version 0.8.1 and later, rewarded ads are offered when you choose View Hint for a recommended shot direction; earlier versions use them for shot-rewind help. In version 0.8.1 and later, interstitial ads may appear between eligible result screens after at least ten completed boards, and are not triggered by elapsed play time alone. Test-ad builds request Google test ads for both formats; live-ad builds request real ads. You can restart and continue playing without using an ad reward.

[Advertising data] Google's advertising SDK may process IP addresses, including approximate location, app and ad interactions, diagnostics, advertising IDs, app set IDs, and applicable device or account identifiers for advertising, measurement, analytics, security, and fraud prevention. Test ads do not mean that SDK network communication is absent. Android ad settings let you reset or delete the advertising ID. Live-ad versions use Google's User Messaging Platform to check consent and provide consent and privacy choices where required.

[Purchases] Google Play processes payments. Remove Ads is a one-time, non-consumable purchase that removes both rewarded and interstitial ads. From version 0.6.3, RevenueCat processes purchase tokens and receipts, product, transaction and purchase-status information, an anonymous app identifier, and SDK environment information such as app and operating-system versions. It uses these to verify and acknowledge Google purchases, restore access, update access after refunds, analyze purchases, and prevent fraud. SDK requests to check purchase access may also occur on app launch. We run no separate developer server, but RevenueCat retains purchase records on its servers. The developer can view purchases and access status in RevenueCat's dashboard. We do not send names or emails as RevenueCat customer attributes, and disable automatic advertising identifier collection and optional SDK diagnostics. We do not send game progress or gameplay records to RevenueCat. The app receives no full card numbers or Google account passwords. Refund updates may be delayed. License testers can use Google test payment methods; ordinary payment methods may incur real charges.

[Support] If you email orbickk@gmail.com, we use the email address, message, and attachments you send to respond and resolve the issue. Do not send passwords, purchase tokens, or complete card numbers. Support correspondence is retained as needed to answer and resolve requests and meet applicable legal retention duties.

[Providers and international processing] Google provides advertising, consent, and Play payments; RevenueCat, Inc. provides purchase verification, access management, and purchase analytics. These providers may process data in the United States and other countries where they operate. See Google's Privacy Policy (https://policies.google.com/privacy), AdMob's data disclosure (https://developers.google.com/admob/android/privacy/play-data-disclosure), and RevenueCat's Privacy Policy (https://www.revenuecat.com/privacy) for their handling, retention, and deletion practices. RevenueCat processes purchase data as a service provider for this app's payment features; we do not connect it to separate advertising or marketing integrations.

[Retention, deletion, and rights] Delete local records through Android's app storage settings. Manage operating-system backups through your device or Google account backup settings. Providers retain purchase records as needed to maintain and restore permanent purchase access, prevent fraud, and meet applicable legal retention obligations, under their policies. Uninstalling alone does not delete Google transaction history or RevenueCat records. Email orbickk@gmail.com to request access, correction, deletion, or restriction of support information or RevenueCat customer purchase records controlled by OrbickK. We request only the minimum information needed to verify the request, never passwords or original purchase tokens. Restoring with the same Play account after deletion may create new records to verify purchase access. Google's transaction records remain subject to Google's separate retention, deletion, and legal obligations.

[Security and sharing] Local records use the operating system's app storage. Google advertising and RevenueCat SDK communications use TLS encryption. OrbickK does not sell personal information. Advertising providers' processing and sharing follow the service policies and user choices described above. Purchase and support information is processed to provide the stated features, resolve issues, fulfill your requests, or meet legal obligations.

[Children's privacy] The game does not knowingly ask children for identifying details such as a name or email address. Parents or guardians can send privacy questions or deletion requests to orbickk@gmail.com.

[Changes and contact] We update this policy when data practices, providers, or features change and provide notice in the app or website when needed. Data controller: OrbickK / Google Play developer name: Orbickk_Lab / Privacy and support: orbickk@gmail.com