1. App and Developer Information

• App name: MO KING Lucky Words Lotto
• Package name: com.moking.luckywordlotto
• Developer / Operator: MO.KING
• Account type: Individual
• Platform and distribution: Android, Google Play
• Privacy contact: mokingdeveloper1@gmail.com

2. Information Processed or Collected

The App has no registration or proprietary user-account system, and the Developer operates no proprietary server or backend. User input and number combinations are processed on the device. External services may nevertheless receive or process information when providing advertising, privacy choices, payments, updates, and official lottery results.

Android backup and device-transfer possibilities are explained in Section 11. The absence of a Developer-operated server does not mean that Google or other external services collect or process no data.

Google Play Data Safety uses its own definitions of collection and sharing, including applicable exceptions. Direct off-device SDK transmissions may require disclosure. The service-provider exception applies under Google's criteria, such as processing on the Developer's behalf and instructions; it does not automatically cover every advertising-related transfer.

3. Information Not Directly Required by the App

The App does not require names, email addresses, telephone numbers, physical addresses, or dates of birth for registration, account creation, or identity verification. It does not request or use precise GPS location.

Users may voluntarily enter names or other personal information in the word-input field. This is not collected as account or identity-verification information, but the entered text may appear in generated results and local records. Users should avoid entering sensitive information or information identifying another person.

4. Purposes of Processing

• Generating lottery combinations using word-based, random, or mixed methods
• Maintaining fixed/excluded numbers and App preferences
• Providing recent results, saved records, and winning-number checks
• Providing advertising, privacy choices, measurement, security, and fraud prevention
• Using local counters and timestamps to manage ad frequency and overlapping displays
• Processing, acknowledging, restoring, and maintaining ad-removal purchases
• Checking for updates through Google Play
• Retrieving official results for the selected lottery

5. Data Stored on the Device

Saved Records: saved_generations.json

Up to 10 saved generation records per lottery type are retained in the App's private storage. One record may contain multiple number combinations.

• Words, names, wishes, or dreams entered by the user
• Creation date/time and record ID
• Lottery type and generation method
• Word-to-number mappings and generated numbers
• Target draw and draw date
• Winning numbers, result-check information, and check time
• Source URL, retrieval failures, and related status

Preferences and Recent Results: app_preferences.json

• Theme and language
• Selected lottery
• Fixed/excluded numbers, enabled status, and retention-on-launch setting
• Related App settings and recent winning-number caches
• App version, installation, and migration status
• The combined generation/result-check completion counter interstitialCompletedActions and pending interstitial opportunity state interstitialPending
• Introductory app-open launch state appOpenCompletedLaunches, last app-open ad timestamp lastAppOpenAdAtMillis, and last full-screen ad timestamp lastFullscreenAdAtMillis
• Ad-removal users' latest result for each lottery, retainedLatestGenerations. This may retain input, generated numbers, generation time/method, draw information, and result-check metadata independently of saved records.

The interstitial completion counter and introductory launch state each use values from 0 to 2. These local states and timestamps control displays within the App and are not sent by the App to a separate analytics server or as advertising targeting data. They are distinct from app/ad interactions independently processed by Google's ad SDK.

Other Local Data

• Ad-removal entitlement stored using mechanisms such as SharedPreferences
• Billing recovery execution and retry status
• Temporary and backup files for reliable storage and recovery
• Local AdMob/UMP consent states and caches
• Cookies, cache, and DOM storage used by result-retrieval WebViews

These App data are not uploaded to a Developer-operated server or cloud database. System backups and external SDK processing may apply separately.

6. Google AdMob / Mobile Ads

The App uses Google Mobile Ads to provide banner, interstitial, and app-open advertisements. App-open ads may appear during launch or return from the background when display conditions are satisfied; they are not guaranteed to appear every time.

No separate third-party mediation SDK or ad source is integrated. The current AdMob mediation setup uses the default AdMob source. This does not mean that all advertisers or advertising technology providers participating in Google's advertising ecosystem are the same entity as the Developer.

For advertising, measurement, analytics, security, and fraud prevention, Google Mobile Ads may process IP addresses, advertising and App Set IDs, other device identifiers, device information, app/ad interactions, and diagnostics. Interactions and diagnostics can include app launches, taps, ad video views, and app/SDK performance information. Actual processing depends on device, region, privacy choices, and Google settings.

The App uses standard ad requests. Ads may be personalized, non-personalized, or limited depending on region, UMP choices, device/Google advertising settings, and AdMob configuration. Declining personalized advertising does not necessarily stop all advertisements. The App does not request ads when UMP does not permit ad requests.

Users with an active ad-removal entitlement do not receive banner, interstitial, or app-open ad requests or displays. UMP status checks and privacy options remain independent of ad display so that privacy choices remain available.

7. Google UMP and Advertising Privacy Choices

The App uses Google's User Messaging Platform (UMP) SDK and Google CMP. During launch, it requests updated consent and privacy-option status and invokes the automatic form flow when Google determines that a consent form is required. This does not force users to repeat the same choice on every launch.

• European regulations message: Published for applicable users in the EEA, United Kingdom, and Switzerland with Consent, Do not consent, and Manage options.
• U.S. state regulations message: Published for applicable regions with choices concerning allowing or opting out of data sale or sharing.
• Privacy-option re-entry: When UMP determines that privacy options are required, the App shows "Ad privacy options" in settings. Users can reopen Google's privacy-option form there.

Google UMP determines applicable regions and whether a message is needed. The country of the selected lottery or the App's display language alone does not determine consent requirements. Message content and language depend on Google's forms and published message settings.

Ad-removal users are not excluded from UMP status updates and can use the same settings entry when privacy options are required. Checking UMP status or opening privacy options does not reactivate their ad requests.

Some U.S. state privacy laws may define certain advertising-related transfers as a "sale" or "sharing." Applicable choices are provided through UMP. Processing varies with region, choices, and Google settings.

8. Google Play Billing and Payments

The App uses Google Play Billing for the remove_ads_lifetime one-time ad-removal product and purchase restoration. It uses product IDs, localized prices, purchase status, pending status, acknowledgement status, and purchase tokens during processing. Purchase tokens are used in acknowledgement requests to Google Play.

The Developer does not store purchase tokens, order IDs, or complete payment-method details on a proprietary server. Ad-removal entitlement and recovery status may be stored on the device, and entitlement can be checked again using Google Play purchase queries.

Credit/debit card numbers, bank-account numbers, payment passwords, and other actual payment-method information are handled by Google Play and are not directly collected or stored by the App Developer. Google's privacy policy and Google Play terms apply.

Clearing App data or uninstalling the App does not erase Google Play purchase history or cancel or refund a purchase.

9. App Updates, Connectivity, and Lottery Sites/APIs

App Updates

The App uses Google Play In-App Update and operates no proprietary update server. Google Play or related Google Play Services may process App version, device/network information, IP address, and technical information necessary for updates.

Android Connectivity Checks

The current Android App reads active-network and validation status provided by the operating system. It does not send separate probe requests to a Google connectivity-check address or the Privacy Policy URL for this determination. Android's own network validation is governed by the operating system and device settings.

A connected network does not guarantee that every advertising, payment, or lottery server will respond successfully. Actual online features communicate with their respective services.

Winning-Number Retrieval

The App communicates with official sites or APIs for the selected lottery. Some official results are retrieved using Android WebView. Lottery type, draw, date, page/request information, IP address, request time, device/network information, and WebView user-agent information may be transmitted to the external service. Site cookies, cache, and DOM storage may be created in WebView.

Words, names, wishes, dreams, fixed/excluded numbers, and generated or saved combinations are not transmitted to lottery sites/APIs. After official results are retrieved, number comparisons take place locally. Information received by external services is subject to their own privacy policies and retention practices.

10. Third-Party SDKs and Services

• Google Mobile Ads / AdMob: Banner, interstitial and app-open ads, measurement, security, and fraud prevention
• Google UMP / Google CMP: Applicable advertising privacy messages and choices
• Google Play Billing: One-time ad-removal purchase, acknowledgement, and restoration
• Google Play In-App Update: Update checking and installation flow
• Google Play Services modules: Supporting related Google features
• Official lottery sites/APIs: Winning numbers and draw information
• Android WebView: Retrieval of certain official results
• GitHub Pages: Hosting this Privacy Policy

The App does not integrate Firebase, Firebase Analytics, separate Google Analytics, or Firebase Crashlytics. The ad SDK's own measurement and diagnostics are distinct from integrating a separate Analytics or Crashlytics service.

Data processed by international services such as Google and GitHub may be processed outside the user's country. Their official policies below explain international processing, retention, and privacy controls.

External links marked ↗ open in a new tab or window.

• Google Privacy Policy
• Google Mobile Ads SDK Data Disclosure
• Google UMP and Privacy Options
• AdMob European Regulations Messages
• AdMob U.S. State Regulations Messages
• Google Play Billing Documentation
• Review Google Play Order History
• Google Play Data Safety
• Android Auto Backup
• GitHub Privacy Statement

11. Data Retention, Deletion, and Android Backup

Recent Results and Saved Records

• Users without ad removal: Previous-session recent results are reset on a new App launch or re-entry through the App icon. This applies regardless of UMP consent or opt-out choices. Separately saved records are not deleted by this reset.
• Ad-removal users: The latest result for each lottery is retained in local preferences and can be restored after closing the App. A new result may replace the previous recent result for that lottery. Recent results and saved records are managed separately.
• Unresolved ownership: A pending or failed ownership check alone is not treated as proof of non-purchase for deleting retained purchaser results.
• Excluded from recent-result resets: Saved records, App settings, UMP choices, and advertising-frequency state are not collectively deleted when recent results are reset.

Saved Records and Advertising State

Saved records may remain until the user deletes them, storage limits replace them, or App data is cleared. Advertising counters, pending state, and recent timestamps persist across launches and are updated by advertising flows. An interstitial opportunity is consumed after a normal ad dismissal is confirmed, not merely because the App closes.

User Deletion Controls

The App allows deletion of individual saved records or records for the selected lottery. Deleting a saved record may leave a separately retained purchaser's recent result or recovery copy. To clear App preferences, recent results, caches, and internal recovery files, users can clear App storage in Android settings. Uninstalling generally removes the App's internal data from the device.

Internal Recovery Copies

Temporary files, rotating backups, and pre-repair copies may retain earlier contents for storage recovery. Deleting a record or resetting recent results does not necessarily immediately and permanently remove all recovery copies.

Android Backup and Device Transfer

If Android backup or device-transfer features are enabled, some App data may be stored in Google's backup system or restored after reinstallation or device transfer. Actual coverage and restoration depend on Android version, device manufacturer, user settings, and system policies. Uninstalling does not guarantee immediate, permanent deletion of every backup copy.

Backup retention and deletion are governed by Google account and Android backup settings and Google's policies. Data handled by AdMob, Google Play, official lottery services, and GitHub is also subject to each provider's retention and deletion policies.

The Developer operates no proprietary user-account server or remote user-data store, so the App has no separate server-account deletion function.

12. Children and Age Requirements

MO KING Lucky Words Lotto is configured on Google Play for users aged 18 and older. It is not designed or offered for users under 18. The App has no date-of-birth collection or age-verification account system. Users should check applicable laws and age restrictions in their country or region. Children or guardians with privacy questions may contact the email below.

13. Security

User input and records are processed in the App's private storage. Official lottery requests directly configured by the App use HTTPS, and result-retrieval WebViews are configured to disallow mixed content. Google SDK transmissions use the respective services' security mechanisms.

The Developer avoids unnecessary personal-information requests and blocks advertising requests for users with active ad-removal entitlement. However, no storage or transmission method can guarantee complete security.

14. External Sites and Links

The App and this document may link to Google services, official lottery sites, and the Privacy Policy webpage. Opening an external page may allow its provider to process an IP address, request details, and browser information. Access to this policy on GitHub Pages is subject to GitHub's privacy practices.

External content, cookies, and data processing are governed by the respective operator's terms and privacy policy. The Developer does not directly control independent providers' retention and deletion functions.

15. Changes to This Privacy Policy

This policy may be revised when App features, SDKs, external services, laws, or platform policies change. Revisions are published at the same official URL with an updated effective date. Important changes will be communicated as required by applicable laws and policies.

16. Contact and Privacy Requests

The Developer cannot remotely view or delete data stored only on a user's device; the App and Android controls in Section 11 are available for local deletion. Requests concerning information held by Google or other providers are subject to their privacy tools and procedures. Do not include unnecessary sensitive information or payment passwords in email inquiries.

17. Official Privacy Policy URL

The official URL for this Privacy Policy is https://mokingapps.github.io/privacy.html .

18. Effective Dates

Initial effective date: September 13, 2026

Revised effective date: September 16, 2026