Privacy policy

Effective date: 2026-01-01

This policy explains how the Nuke Codes 76 Android release application, Firebase-hosted web application, and GitHub Pages-hosted web application handle information.

Information handled by the application

Nuke Codes 76 does not require an account or sign-in to retrieve and display launch codes. The application does not ask you to enter a name, email address, or other profile information for that journey.

The application handles the following information and technical data:

• Local storage: the application stores launch codes and related timing information on your device or in your browser to support recovery from network failures. This is not an account or player activity history.

• Code-service requests: Android and both web applications request launch codes from the Nuke Codes 76 code service. The application does not add an account identifier. The service and its hosting infrastructure may process IP addresses, request headers, timestamps, and technical logs to deliver and protect the service.

• Web hosting requests: the Firebase-hosted web surface uses Firebase Hosting infrastructure. The GitHub Pages-hosted web surface uses GitHub Pages and GitHub infrastructure. Loading either surface sends ordinary web requests to its configured hosting provider.

• Clipboard: copying selected launch-code text places it on your system clipboard. Copying does not cause the application to transmit the selected text.

• Connectivity state: the application checks network availability to retry failed code requests.

Android advertising

The Android release application uses Google Mobile Ads (AdMob) to request and display a banner advertisement. Google and its advertising partners may process device and app information, IP address, advertising identifiers where available, approximate location derived from technical signals, and ad interactions to provide, measure, secure, and improve advertising. Advertising treatment may depend on Google account settings, applicable regional requirements, and provider configuration.

The Firebase-hosted and GitHub Pages-hosted web applications do not request or display this banner ad and do not run the Android advertising-consent journey.

The Android application uses Google's User Messaging Platform (UMP) to present advertising consent forms and privacy options when required, including modification or withdrawal of advertising choices. Refusal may still permit restricted advertising; it does not necessarily prevent all ads. These choices do not prevent access to launch codes and do not control separate Analytics, Crashlytics, or Performance Monitoring processing.

For information about Google's handling and available advertising controls, see How Google uses information from sites or apps that use its services and Google's advertising controls.

Analytics, diagnostics, and performance

Nuke Codes 76 uses Google Firebase services. Depending on the platform, these services may process app-instance or device information, IP addresses, app interactions, screen navigation, crash and error details, performance measurements, and related technical diagnostics.

• Android: Firebase Analytics processes app interactions and navigation, Firebase Crashlytics processes crashes and application errors, and Firebase Performance Monitoring processes performance information. Advertising providers may also process advertising measurements and diagnostics.

• Firebase-hosted web and GitHub Pages-hosted web: both use Firebase Analytics. Neither uses Firebase Crashlytics, Firebase Performance Monitoring, or Android banner advertising.

The application does not set an application-defined user ID for these services. However, provider-generated identifiers and technical signals may still be used by Google to operate these services. Nuke Codes 76 currently does not provide an in-app telemetry-consent or telemetry-opt-out control.

See Google's privacy policy and Firebase privacy and security information for more information about provider processing and controls.

Android also sends sanitized advertising and consent-error diagnostics to Firebase Crashlytics for troubleshooting. These contain limited technical information about errors, application and advertising state/configuration, and timing and performance. The application excludes raw provider content, user or device identifiers, and consent choices or strings from these diagnostics. These limits do not apply to separate Firebase or advertising-provider processing described above.

Android writes limited technical information about failed code requests to the device console for troubleshooting. These application-produced records do not contain personal data, user-linked identifiers, or launch codes. This local diagnostic path does not transmit or automatically export these records or store them in application-managed persistent storage. These limits do not describe platform-added log metadata or platform-controlled retention. Separate Firebase and provider processing described above remains unchanged.

Accounts and cloud data

The launch-code journey does not require sign-in or create a user account.

A scheduled cleanup attempts to remove legacy or accidental user records in Firebase Authentication and Firestore. The current application has no path to create these records. This does not guarantee that no legacy records remain.

How information is used and shared

Information is processed as needed to:

• retrieve, cache, validate, and display current launch codes;

• provide and measure Android advertising;

• understand application navigation and operation;

• detect, diagnose, and correct crashes, errors, and performance problems; and

• operate, secure, and protect the application and its supporting services.

Technical data is transmitted to service providers that perform these functions, including Google services such as AdMob, Firebase Analytics, Crashlytics, Performance Monitoring, Firebase Hosting, and related cloud infrastructure. The GitHub Pages web surface uses GitHub Pages and GitHub infrastructure. Requests for launch codes are transmitted to the configured Nuke Codes 76 code service and its hosting infrastructure. These providers process data under their own terms and privacy policies and may use subprocessors.

Retention

The local launch-code cache remains in application or browser storage until it is replaced, cleared through platform or browser controls, or removed when the application's storage is deleted.

Analytics, advertising, crash, performance, hosting, and network records are retained according to the applicable provider configuration and provider policies. Contact the developer if you have a question about a record controlled directly for Nuke Codes 76.

Security

Configured code-service requests use HTTPS. Access controls restrict changes to service data and access to legacy user records. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.

Your choices and requests

You can:

• modify or withdraw advertising choices through advertising privacy options when required and available in the integrated Android version;

• use operating-system or browser controls to clear the application's local storage;

• use device, browser, and Google controls that apply to advertising and analytics;

• choose not to use the application if you do not want the described processing; and

• contact michal.kapusnik@gmail.com with a privacy question or request.

There is no Nuke Codes 76 account to delete through the application. If you make a request, additional information may be needed to understand and respond to it. Provider-controlled information may need to be addressed through the provider's available controls or request process.

Changes to this policy

This policy may be updated when the described processing or applicable legal requirements change. The effective date above identifies the current policy version.

Contact

Nuke Codes 76 is developed and provided by Michal Kapusnik.

For privacy questions or requests, contact michal.kapusnik@gmail.com.