THE CURRENT TEST VERSION

Your data.

This page explains what the current StackDare test version stores. It will be updated before the public launch or the addition of advertising.

Guest profile and scores

The server stores a randomly assigned player ID, your editable player name, your optional country, a hashed session token, scores and timestamps. Your player name and best scores appear in the leaderboard to people who can access the game.

On your device

A first-party session cookie keeps access to your guest profile for up to one year. Local storage remembers your language, sound preference and local records. The installed web app caches game files for offline use. Clearing site data removes your local access, but does not delete server-side scores.

Checking a run

At the end of a ranked run, tap timings are sent to the server to reconstruct the score. Run tickets are retained for up to two hours and cleaned up when new runs start. Guest profiles and leaderboard records currently have no automatic expiry.

Advertising and external services

Google Analytics is optional and loads only after you allow it and the server enables it. Internal beta evaluation separately records game and feedback events with a random session identifier, timestamp and your player profile when available. Fonts may be loaded from Google Fonts; those requests disclose technical connection information such as your IP address to that provider. Hosting providers also process connection data needed to serve the site.

Optional tcomGames accounts

Google sign-in is optional. When you choose it, Google processes your authentication and shares a verified email address and account identifier with tcomGames. We store these with your player profile, role, account status and login timestamps. We do not receive or store your Google password. Your email is visible only to you and authorised administrators.

Signing in transfers this browser’s guest scores to your account, keeping the better score per leaderboard. Session cookies are secure, HTTP-only and expire after 30 days. Sign out on all devices to revoke them immediately. Google sign-in takes place on the central tcomGames domain. After your confirmation, a short-lived, single-use code establishes a separate session on the registered game domain. No Google token is sent to the game.

Temporary login records expire after 10 minutes and are cleaned up on subsequent sign-in attempts. Login rate-limit records use a time-bucketed hash of the connecting IP and are cleaned up after expiry. Administrative role changes and suspensions are recorded in an audit log. Account data and audit records do not yet have an automatic deletion schedule. Contact games@tognella.com for account and deletion requests.

Memdrix results

Memdrix stores issued patterns, run state and timestamps to check each result. Run tickets expire after two hours and are cleaned up when new runs start. Confirmed bestscores and achievement activity stay with your guest profile or account; earlier local scores are not imported. Signed-in accounts earn Coins for confirmed patterns and once-only milestones; those credits stay in the account ledger. Device storage remembers the optional sound setting and feedback-invitation counter. Memdrix beta event context contains round, points, mistake count and active solving time, not patterns, cell selections, names or email. These beta events are separate from optional Google Analytics.

Coins Shop data

For account purchases we store the selected product and its name at purchase, Coin price, ledger reference, time, purchase request key and ownership. Your inventory and selected profile cosmetics follow your account across supported game domains. Product changes are recorded in the existing admin audit. The browser temporarily keeps an account-scoped pending purchase key in session storage to recover uncertain responses; no payment details are collected. The shop introduces no additional analytics or required tracking consent.

Activated shop cosmetics are displayed with your public player name in leaderboards and existing Latest achievements entries. You can deactivate them in My extras. Email, wallet balance and purchase history remain private. Buying cosmetics does not create an achievement.

Your current avatar selection and the last game you visited while signed in are stored with your account to personalise your entry. This preference contains one game ID, not a visit history. Avatar previews do not purchase items. Purchased components remain in your account; saving equips only free or owned parts. Your public avatar appears with your player name on leaderboards and existing community achievements.