Privacy Policy

This Privacy Policy explains how the Android application covered by this page handles information. It describes the information processed on the device, the information handled by advertising services, and the choices available to users.

Last updated: July 29, 2026

1. Information processed on the device

The application may store the following information locally when a user enters or creates it:

• Participant names
• Result or penalty labels
• Game settings, such as run speed, reveal mode, mask setting, and ladder density
• Current game state and saved result records created by the user

This information is used only to provide the ladder, restore the user's local game state, display results, and manage saved results. The application does not send participant names, result labels, or game settings to a developer-operated server.

If a user enters a real person's name, contact information, or other sensitive information into a participant or result field, that information may be stored locally on the device. Users should avoid entering information that is not necessary for the activity.

2. Purposes of processing

Information handled by the application is used for the following purposes:

• Showing participants, results, and penalties
• Generating the ladder, calculating paths, and matching results
• Restoring the user's locally saved game state
• Saving, displaying, and deleting result records at the user's request
• Creating a result image and sharing it through an external app selected by the user
• Sharing an app link, opening the app store for rating, or opening this policy when the user selects those actions
• Measuring feature use and application performance after the applicable analytics consent state permits collection
• Displaying banner and interstitial advertisements

3. Local storage and retention

The application uses Android's local application storage to save game state and saved result records. This storage is not a developer-operated cloud database and is not synchronized through an application account.

• Game data remains on the device until the user edits or deletes it, clears the application's data, or uninstalls the application.
• Saved result records can be deleted from the application's saved-results screen.
• Result images created for sharing are written to an application cache directory and may be removed by the operating system or by storage cleanup.
• Depending on Android backup settings and device configuration, local application data may be included in an operating-system backup. Such backup is controlled by Android or the device provider, not by a developer-operated server.

4. Sharing and external applications

When the user chooses to share a result image, the application creates a temporary PNG image and opens the Android Sharesheet. The image may contain the participant names, participant numbers, and result labels currently selected for sharing. The image is sent only to the external application or service that the user chooses.

When the user chooses to share the application, the application sends a text message containing an app link. The application may also open the app store or an external web browser for rating or for viewing this policy. Processing after the user leaves the application is governed by the privacy policy of the selected external app or service.

5. Advertising and Google Mobile Ads SDK

The application uses Google Mobile Ads SDK (AdMob) to display banner and interstitial advertisements. The SDK may automatically collect and share information with Google and its advertising partners for advertising, analytics related to the advertising service, diagnostics, security, and fraud prevention.

Depending on the SDK configuration, the user's region, and the user's consent choices, the information may include:

• IP address, which may be used to estimate a device's general location
• Product interactions, such as app launches, taps, and interactions with advertisements
• Diagnostic information about application or SDK performance, including launch time, hangs, and energy use
• Device or other identifiers, including the Android Advertising ID and app set ID

Google states that information collected by the Google Mobile Ads SDK is encrypted in transit using TLS. The Android Advertising ID can be reset or deleted through Android settings, subject to the controls provided by the operating system.

For more information, see Google Mobile Ads SDK data disclosure and Google's Privacy Policy.

6. Firebase Analytics

The application uses Google Firebase Analytics to understand whether core features work as intended and how users move through the application. Analytics collection is disabled by default and is enabled only after the application's consent flow reports a state that permits analytics storage. If consent is denied, unavailable, incomplete, or cannot be interpreted, analytics collection remains disabled.

When collection is permitted, Firebase Analytics may process:

• Application lifecycle and engagement information automatically provided by Firebase
• Screen names within the application, such as game, menu, settings, edit, and results screens
• Feature events such as starting or completing a ladder run, creating a new ladder, viewing all results, saving a result, selecting a share target, and attempting to show an interstitial advertisement
• Limited categorical or numeric details, such as participant count, winner count, result mode, run type, completion count, save outcome, share content type, and advertisement-attempt outcome
• Device, application, and diagnostic information that Firebase Analytics processes automatically under Google's service terms and documentation

The application does not include participant names, user-entered result or penalty text, exact participant-to-result mappings, saved-record identifiers, ladder seeds, search text, shared image contents, file paths, URIs, selected share-target packages, consent strings, advertising unit identifiers, exception messages, or stack traces in its custom analytics events.

Advertising ID collection for Firebase Analytics is disabled in the application configuration. Default ad-personalization signals and Firebase automatic screen reporting are also disabled; the application records only its defined Compose screen routes. Analytics data is transmitted to and processed by Google. Retention and deletion of data already received by Firebase are governed by the configured Firebase/Google Analytics settings and Google's applicable policies.

For more information, see Firebase privacy and security information, Firebase Analytics documentation, and Google's Privacy Policy.

7. Consent and privacy choices

The application uses Google's User Messaging Platform (UMP) SDK to update consent information at app launch, show a consent form when required, and provide a privacy-options entry point when required.

Before the consent state allows ad requests, the application does not initialize Google Mobile Ads or request banner or interstitial ads. Depending on the user's region and choices, Google may serve personalized, non-personalized, limited, or other permitted forms of advertising.

When the UMP SDK indicates that privacy options are available, the application provides a Privacy options entry in Settings so the user can review or change the available choices. The application re-evaluates analytics collection after this flow. If the resulting state does not permit analytics storage, new analytics events are not collected. Events that occurred while collection was disabled are not queued or sent later.

Consent and privacy-choice information is handled by Google through UMP, advertising, and analytics services according to the choices presented and Google's applicable policies.

For more information about UMP and ad-serving modes, see Google's UMP SDK guidance and Google's ad-serving modes guidance.

8. Permissions

The application does not request access to contacts, precise or approximate device location, camera, microphone, calendar, health information, or financial information for its own features. Network access is used by Google Mobile Ads when advertising is permitted and by Firebase Analytics when analytics collection is permitted.

9. Information shared with third parties

The developer does not sell or provide user-entered participant names, result labels, or game settings to a developer-operated server. Google Mobile Ads SDK may transmit and share advertising-related information as described in Section 5. Firebase Analytics may transmit analytics information to Google as described in Section 6 when collection is permitted. A user-initiated share may also transfer the selected result image or app link to the external app or service chosen by the user.

10. Children's privacy

The application is not directed to children under 13. It does not provide child accounts, login, or a developer-operated service for knowingly collecting children's personal information. If you believe that a child has provided personal information through the application, please contact us using the address below.

11. Security

The application stores its own game data in Android application storage and does not operate a server containing that data. Data transmitted by Google Mobile Ads SDK and Firebase Analytics is subject to Google's transport and security practices. No method of storage or transmission is completely secure, so users should protect their device, keep Android up to date, and review content before sharing it.

12. Changes to this Privacy Policy

This Privacy Policy may be updated when application features, advertising services, legal requirements, or applicable policies change. Any updated version will be published on this page.

13. Contact

For questions about this Privacy Policy or the handling of information, contact:

• Developer: Logan CHOI
• Email: weimaraner.logan.choi@gmail.com