Local Storage Usage
The game source explicitly uses localStorage to store the settled balance and fractional carry state. This allows the demo to preserve your virtual coin balance between page reloads without requiring an account login.
- Settled Balance: Stored locally to reflect your current virtual coin count.
- Fractional Carry: Persists through settlement, manual refill, and reload as per the contract.
Clearing cached files may leave local storage intact depending on browser settings. The presence of local storage does not prove that no personal data are processed elsewhere.
Font Declarations
The demo template declares a Google Fonts stylesheet. This request is made by the browser when loading the page.
- Scope: Limited to rendering text elements.
- Observation: Actual full-site network capture remains pending in this independent review.
External font requests do not inherently imply user tracking, but they do involve third-party domains. The public HTML also declares a Statinside counter script and noscript pixel. Their presence does not establish the full runtime processing scope.
Identity and Anonymity
Because the demo uses localStorage for balance persistence and has no account login flow, it does not require personal identification. However:
- This does not establish anonymity across all sessions if cookies or other storage mechanisms are used.
- It does not confirm that no data is collected, sold, or processed by third parties.
- The demo is not a verified identity provider.
The game uses fixed localStorage keys for its balance and fractional carry within this site’s browser storage. Those keys are not evidence of a unique user identifier.
Data Collection Scope
The observed data usage is limited to:
- Balance State: Stored locally in localStorage.
- Font Rendering: Requested from Google Fonts.
No other data collection (e.g., mouse movements, click patterns, or IP logging) is explicitly confirmed by the source code in this demo view. The absence of visible collection points does not prove their absence.
Third-Party Requests
The public page declares Google Fonts resources, a Statinside counter script at https://statinside.com/counter.js, and a noscript image at https://statinside.com/pixel.png?id=44. These source declarations do not establish all runtime requests or the providers’ retention and processing policies.
| Resource | Type | Purpose |
|---|---|---|
| Google Fonts | Stylesheet | Text rendering |
Other network requests may exist but were not captured in this specific demo instance.
Limitations of This Guide
This privacy overview is based on source-observable facts from the demo as provided. It does not:
- Claim to represent the privacy policy of any outside company.
- Guarantee that no data is sold or shared.
- Confirm that data is processed exclusively locally.
- Establish legal rights or regulatory compliance.
For complete privacy terms, refer to the official source if available. This demo is an independent demonstration tool.
Frequently asked questions
Does using localStorage mean I am anonymous?
No. While the demo uses localStorage for balance and does not require login, this does not guarantee anonymity. Other tracking methods (cookies, fingerprints) may still be in use. The presence of local storage does not exclude other data processing.
What data is stored locally?
The demo stores your settled balance and fractional carry state in localStorage. This allows persistence across reloads. No other personal data are explicitly confirmed as stored locally in this demo.
Is my data processed exclusively locally?
Not necessarily. While balance data is stored locally, the demo requests Google Fonts from an external server. This does not confirm that all data processing is local or that no data is sent to third parties.
