Because the demo lacks account controls, the absence of visible personal data processing does not prove that no other data are collected elsewhere. The following section describes only the storage mechanisms and requests observed within this specific demo environment.
Local Storage and Persistence
The demo uses browser localStorage to persist specific state data. This storage mechanism keeps data locally on your device even if you close the browser window.
- Settled Balance: Your final virtual coin balance after a completed round is saved. If the balance reaches zero, it persists locally as zero.
- Fractional Carry: Any fractional value remaining after a settlement persists across refill and reload events.
- Unfinished Rounds: If the page is reloaded during an active match, the round ends without refund and does not resume.
Clearing cached files may leave local storage intact depending on your browser settings. This storage does not establish anonymity, nor does it guarantee that your data are not processed by other means.
Third-Party Requests
The public HTML declares Google Fonts resources and embeds a StatInside counter script and noscript pixel. Actual browser request capture is pending; this is not a claim that other requests or processing are absent.
- This source inspection does not establish all third-party involvement, runtime requests, or data retention practices.
Wallet and Balance Restoration
The demo wallet has an initial balance of 1000 virtual coins. These coins have no cash value and cannot be withdrawn.
| Feature | Detail |
|---|---|
| Restoration Type | Manual idle-only restoration |
| Eligibility | Available while idle |
| Threshold | Balance below 10 |
| Result | Sets balance to exactly 1000 |
This restoration is a manual action that sets the balance; it is not automatic replenishment. There is no account recovery, cash withdrawal, or network-synchronised account linked to this balance.
Data Collection Scope
Privacy claims are limited to what is observable in this demo. The demo has no account-login flow. This does not establish whether other page services associate identifiers with a visit.
- Anonymity: Not promised. Local storage is device-specific but not necessarily anonymous.
- Profiling: No claim is made regarding the absence of profiling.
- Marketing: No claim is made regarding the absence of marketing communications.
Terms of this guide explain its own scope; they do not invent legal releases or establish an outside company's policies.
Audience and Responsibility
The intended audience for this guide is 18+. This is a policy guideline, not a claim about local law or an implemented age gate.
Responsible use involves managing your own time and virtual coin limits. This demo does not clinically train behaviour, nor does it make losses safe. There are no account-level blocking, timer, or self-exclusion tools implemented in this specific demo interface.
Game Mechanics Context
The Move To Front Ranks game operates independently of identity. The following rules apply to the privacy of the data generated during play:
- Scoring: Starts with an ordered alphabet 0,1,2,3. Scores are based on sum of squared current ranks, moving each observed code to the front.
- Data Persistence: The current virtual-coin balance and fractional carry are stored in localStorage. Raw scores and unfinished match state are not saved by the game.
- No External Sync: Play is not synchronised to a central account; progress is local.
Frequently asked questions
Does the demo store personal data?
The demo uses localStorage to store your settled balance and fractional carry. This is local to your browser. It does not establish anonymity, and the absence of account controls does not prove that no other personal data are processed elsewhere.
How is my balance restored?
When the balance falls below 10 while idle, a manual restoration sets the balance to exactly 1000. This is not an automatic refill or a cash withdrawal. Unfinished rounds do not refund on reload.
Is the demo anonymous?
No anonymity is promised. While there is no login, data stored in localStorage is tied to your device. Third-party requests like Google Fonts may also occur, though their specific data handling is not fully confirmed in this scope.
