GUEST OR ACCOUNT · YOUR CHOICE

Your logbook & data.

This page describes the Tideguard 0.25 single-player playtest. Play without registering using a browser save, or create an account for a cloud save. There are no payments, advertisements or third-party analytics in this build.

Guest saves

Guest progress uses localStorage under tideguard.progress.v1. It stores completed runs, victories, highest wave reached, pearls, supply and lighthouse upgrades, combat seconds, save version and sound preference. Guest-only progress is not sent to the account API. Campaign and expedition preparation checkpoints are also saved locally for the current player. An interrupted wave restarts from preparation. These battle checkpoints are not sent to the cloud.

A different device or browser, private browsing, clearing site data or moving to a new domain can start a new guest record. Damaged or unsupported local data triggers a recovery notice and a fresh logbook. If browser storage is blocked or full, progress may last only for this visit.

Language choice is stored separately in this browser under tideguard.language. It does not change the cloud save format.

Battle checkpoints can remain after signing out, separate from the account recovery copy. They are shown only for their matching player. Clear Tideguard browser data below to remove all local checkpoints. A Home Screen web app may use separate browser storage.

Accounts and cloud records

The server stores your username, a salted scrypt password hash, registration time and latest successful login time. It stores your chosen game record, a revision number and last cloud update time. Do not include sensitive or personal information in your username.

This playtest has no email collection, email verification, email delivery or password recovery. Keep your username and password safe. The original password is not stored in readable form.

A session cookie keeps you signed in for up to seven days unless you sign out. Production session cookies are Secure, HttpOnly and SameSite=Strict. A separate protection cookie checks same-origin submissions. These cookies are necessary for account functions.

Choosing and synchronizing a record

After signing in, explicitly choose the browser or cloud record. Choosing the browser record replaces the cloud record; choosing cloud keeps that record active. Guest progress stays separate. Records are not automatically merged.

Account play keeps a browser recovery copy and an account identifier in Tideguard-specific localStorage keys. Completed runs, workshop purchases and sound changes trigger cloud saves. Failed saves keep pending changes in that recovery copy when browser storage is available. Use Retry cloud save after reconnecting. If another device changed the record, compare and choose a copy on the account page.

Account recovery data can remain on a shared browser. Sign out when finished: signing out removes that account’s browser recovery copy and marker when no unsynced changes remain. Closing the browser alone does not necessarily end the session.

What game statistics mean

Completed runs, wins, best wave and combat seconds are cumulative values reported by the game client. Combat seconds exclude pauses, preparation and abandoned runs; at 2× speed they count real combat time. An imported local record may include play before account registration. These are playtest counters, not verified anti-cheat telemetry.

A separate, token-protected read-only operations report shows account registration and latest login times, cloud update times and game counters. Guest-only play is absent. Account timestamps are server-recorded. The web report shows at most 500 accounts; an operating-system-protected management command can report all records.

Hosting, security and retention

The host processes normal connection information, including IP addresses and requested pages. Application login limits use keyed hashes of the observed network address and username. Rate-limit rows are pruned after an hour when subsequent limited activity occurs. Reverse-proxy configuration can make several players share the same observed network address and limit.

Accounts and records remain in the deployment database until removed by the operator. Backups can retain older records according to deployment operations. This build sets no automatic account deletion or backup retention schedule and makes no claim of legal compliance. There is no self-service account deletion or recovery interface. Clearing local data does not delete cloud records or backups.

Clear Tideguard browser data

Close other Tideguard tabs first. This removes guest progress, account recovery copies, account markers and battle checkpoints in this browser. It does not delete cloud records or sign out a server session. To end a session, sign out on the account page first.

Read the game guide or manage your account and saves.

Local battle reviews and island medals

Map and difficulty preferences, the most recent completed battle report and island medals stay in this browser. They are not uploaded with cloud records. Clearing site data removes them; an active run is still not saved.

Local challenge records

Challenge preference and separate challenge medals stay in this browser and are not uploaded with cloud progress. Reports include the chosen challenge and snare counters. Clearing site data removes these local records. Completed challenge runs still update ordinary cumulative records, pearls and wins; active runs are not saved.

Reports also record relocation count and transport gold. These report fields stay on this device with the rest of the battle review; cloud progress is unchanged.

Combat-number preference is saved in this browser and does not sync with account progress. Defense view is a temporary display setting. No new cloud fields are added.

Practice creates no completed-run or report record. The early-launch counters belong to the browser-local battle report; cumulative account records keep the existing save format.