Guide

Privacy and Data in the Demo

The official website of 44k.

The official website of 44k. This guide observes the data storage and network requests made by the Binary Order demo for the 44k brand. The demo operates in your browser without an account or payment flow. The observations below describe what is actually visible in the source code and local environment; they do not constitute a comprehensive privacy policy for an outside service.

Local Storage Usage

The game source explicitly uses localStorage to persist the following data:

  • Settled virtual balance.
  • Fractional carry amounts.

These values remain in your browser even after a reload. However, the presence of local storage does not establish that your identity is anonymous, nor does it prove that no personal data are processed elsewhere. It also does not guarantee that the data are not sold or shared with third parties.

Network Requests

The template declares a stylesheet from Google Fonts. This indicates that font files may be requested from Google’s servers when the page loads. The full network traffic capture for the entire site is not yet available in this guide’s source review. Therefore, additional data requests (such as analytics or telemetry) cannot be fully confirmed from this page alone.

Account and Payment Data

The demo has no account login flow and no payment flow. Consequently, there is no explicit collection of email, name, or payment details within the demo interface. The absence of these controls does not prove that no personal data are processed; it only means they are not required for this specific virtual-coin experience.

Third-Party Processing

Based on the observed source:

  • Google Fonts is declared, implying potential processing by Google for font delivery.
  • The deployed HTML also declares a StatInside counter script and a noscript tracking pixel. Full network behavior and retention remain unverified.

Clearing cached files alone may leave localStorage intact; use site-data controls to remove saved game data, but other tracking mechanisms (like cookies or fingerprinting) are not confirmed by this guide’s current scope.

Data Retention and Anonymity

This guide does not promise anonymity, no sale of data, or exclusive local processing. The local storage is visible to the browser, meaning local malware or other scripts on the same domain could potentially access it. Retention policies for any data sent to third parties (like Google Fonts) are not detailed here.

Scope of This Guide

This privacy description is limited to the source-observable facts of the demo. It does not invent a legal release or establish the policies of an outside company. The 18+ audience note is a guide policy, not a legal age gate.

Frequently asked questions

Does using localStorage mean I am anonymous?

No. localStorage only stores data in your browser. It does not prevent the site from collecting other data or sharing it with third parties. Anonymity depends on broader tracking practices not fully visible here.

What data is stored locally?

The demo stores your settled virtual balance and fractional carry amounts. These persist across reloads but are not synced to a cloud account.

Are third parties involved?

Yes. The template declares Google Fonts, which may send your browser’s IP and other data to Google. The HTML also declares a StatInside counter script and noscript tracking pixel; complete network behavior and retention are not established here.