Privacy Policy for Nuke Codes 76

Effective date: 2026-01-01

Nuke Codes 76 is developed and provided by Michal Kapusnik. This policy explains how the Nuke Codes 76 Android release application, Firebase-hosted web application, and GitHub Pages-hosted web application handle information.

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

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:

• Launch-code data stored on your device: the three current launch codes, their validity time, authority and validation times, and cache-age metadata. This data is stored through the platform's application-preferences storage so that the application can recover safely from network failures. It is not an account or a user history.

• Code-service requests: the Android release application and the default web build deployed through Firebase Hosting request current launch-code data from https://codes.kapusnik.cz/v2/nuka. The web build deployed through GitHub Pages requests it from https://api-dev.codes.kapusnik.cz/v2/nuka. The application does not add an account identifier to these requests. The configured code-service and hosting infrastructure may process ordinary request information, such as an IP address, request headers, timestamps, and technical logs, when delivering and protecting 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 data: you can select launch-code text with native text selection. When you choose the platform's Copy action, it places the selected text on the system clipboard. The selection can contain part or all of the displayed code. The application does not provide its own card-copy action or clipboard-write handler. The application does not use platform Copy to send the selected text elsewhere.

• Connectivity state: the application observes whether a network connection is available so it can retry a failed code request. It does not use this state to create an account or profile.

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. The exact ad treatment can also depend on Google account-side settings, regional requirements, and remote provider configuration that is not stored in this repository.

The Firebase-hosted and GitHub Pages-hosted web applications do not request or display this banner ad. Nuke Codes 76 currently does not provide an in-app advertising-consent control.

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 and build configuration, those services may process app-instance or device information, IP address, app interactions, screen navigation, crash and error details, performance measurements, and related technical diagnostics.

• Android: release builds initialize Firebase Analytics navigation observation, enable Firebase Crashlytics for captured application errors, and include Firebase Performance Monitoring. Android advertising can also produce provider-controlled measurement and diagnostic events.

• Firebase-hosted web and GitHub Pages-hosted web: the shared web host page initializes Firebase Analytics. Neither maintained web surface enables Firebase Crashlytics, Firebase Performance Monitoring, or the Android banner-ad integration.

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.

Accounts and cloud data

The launch-code journey does not use Firebase Authentication, require sign-in, or create a user account. Although the web host loads Firebase Authentication and Firestore libraries, the current application code does not use them for the launch-code journey.

A scheduled maintenance process removes legacy or accidental /users records and attempts to remove the matching Firebase Authentication record before it deletes each Firestore record. The current application has no path to create these records. The application source alone does not establish whether any legacy provider-side record exists at a particular time.

The application's refresh service stores one current launch-code dataset and up to 52 superseded datasets in Firestore for operational continuity. Those datasets contain launch codes and validity information, not application account or profile fields. They are service data rather than a history associated with an individual player. Repository access rules deny client access to historical datasets and to the legacy /users collection.

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. The operational Firestore launch-code history is bounded to the latest 52 complete superseded datasets.

Analytics, advertising, crash, performance, hosting, and network records are retained according to the applicable provider configuration and provider policies. A single provider-controlled retention period cannot be stated from the application source alone. Contact the developer if you have a question about a record controlled directly for Nuke Codes 76.

Security

The identified code-service URLs use HTTPS. Firestore rules allow retrieval of a valid current launch-code dataset, deny listing or writing code records, deny client access to operational history, and deny client access to /users. The application does not attach an account identifier to its launch-code requests. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.

Your choices and requests

You can:

• 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 application behavior, service-provider configuration, legal requirements, or publication details change. The effective date above identifies the current policy version.