Before you clear your browser: game progress

A result on screen is not necessarily a saved game

Before closing a game, look for an explicit explanation of saving, checkpoints, export, or account synchronization. A score shown at the end of a round may describe only that round. A game can also keep settings while discarding the current attempt. Do not treat either behavior as proof that progress is backed up.

AGICADE’s brand hub does not store game progress or provide a recovery account. Each game runs on the separate Games service. This guide explains the questions to ask; it does not claim that every AGICADE game uses the same storage method.

What “saved in this browser” can mean

One browser mechanism, localStorage, keeps data for a website’s origin across browser sessions. Private-session localStorage is cleared when the last private tab closes. Browser settings can also prevent storage. These behaviors are documented in MDN’s localStorage reference.

That is a browser capability, not a promise that a particular game uses it. If a game does save locally, do not assume that opening a different browser, profile, or device will carry the data with you. Look for an explicit export or sync feature before changing where you play.

Check a save before relying on it

If a game explicitly says it saves progress, test that promise with a low-stakes attempt first. Note the exact point you expect to return to, follow the game’s save instructions, and wait for any confirmation it provides. Only if you are comfortable losing that test attempt, close and reopen the game in the same browser profile. Compare the result with the point you recorded.

Returning to the same level establishes only what happened in that test. It does not demonstrate cloud synchronization, recovery after clearing site data, or a permanent backup. If the result is different, record whether the game restored a checkpoint, only a score, or nothing. Ask about that specific behavior before risking a longer session. This is a procedure you can choose to try, not a claim that we have tested saving in each AGICADE game.

A decision checklist before a reset

1. Identify the action. Reloading a page, restarting a round, clearing site data, and deleting a browser profile are different actions. Read the confirmation message instead of treating all of them as a harmless refresh.
2. Find the game’s save instructions. Check whether the current run, only completed levels, or only settings are saved. If the instructions do not say, treat persistence as unconfirmed.
3. Use a supported backup if available. If the game offers export, follow its instructions and keep the file somewhere you can find. Do not paste storage values into unknown websites.
4. Try the least disruptive troubleshooting step. For a missing sound or input problem, use the relevant browser check before deleting anything.
5. Decide what loss you can accept. If the current run matters and you cannot confirm a save, stop before clearing data. Ask through the contact page, without assuming recovery is possible.

If progress already appears to be missing

First check that you opened the same game on the same browser profile and device as before. A different profile can look like a fresh start. Note whether you recently used private browsing, cleared site data, changed devices, or selected a reset control. Those details help distinguish possible causes without guessing.

Keep the original device and profile unchanged while you check the game’s own recovery instructions. If no backup or sync mechanism exists, local progress may not be recoverable. This hub cannot reconstruct a saved game from a screenshot of a score.

Shared devices need a separate decision

A saved game may be convenient on your own device and undesirable on a shared one. Decide whether leaving game data there is acceptable before you start. The right choice depends on the game’s documented behavior; private browsing is not a substitute for a durable backup.