Browser games can save progress without installing a traditional desktop application, but “saved in the browser” describes several different systems. A title might use local storage for a few settings, IndexedDB for structured progress, a cookie for a session identifier, or a provider account for a server-side save. An embedded game also runs under a different web origin from the page that displays it. Understanding those boundaries helps prevent accidental data loss and makes save problems easier to describe.
The origin controls the storage boundary
Web storage is separated by origin, which normally combines scheme, hostname and port. Data created by a game delivered from Playgama belongs to the provider origin rather than spinappy.com. Clearing Spinappy's local storage can remove the external-game preference but may not remove the game's own progress. Clearing all browser data can remove both.
This separation is a browser security feature. One unrelated website cannot simply read another origin's local storage. An iframe is still subject to browser storage and privacy rules, and strict tracking protection may restrict third-party storage. The exact behavior can differ by browser and user setting.
Cookies are not the same as local storage
Cookies are small values that can accompany network requests to their matching domain. They are commonly used for sessions and preferences. The Web Storage API provides localStorage and sessionStorage values that JavaScript can read for the same origin. localStorage usually remains until it is cleared, while sessionStorage is associated with a tab session.
Neither mechanism is ideal for large, complex saves. IndexedDB is a browser database API intended for larger structured data and offline-capable applications. A game engine may hide these implementation details, so the browser's developer tools are often the only visible indication of which storage system is in use.
Cloud saves and local saves behave differently
A local save exists only in a particular browser profile and storage partition. It may not appear on another device, another browser, a private window, or a newly created browser profile. A cloud save is associated with a provider or game account and can be restored after authentication if the game supports it.
Spinappy does not provide a player account and does not claim to synchronize partner game progress. If a game offers account-based progress inside its iframe, that feature belongs to the game or distribution provider. Check the game's own interface before assuming a save will move between devices.
Why progress sometimes disappears
The most common causes are clearing browsing data, using private browsing, changing browser profiles, blocking third-party storage, or loading a different origin. Provider migrations can also change a hostname or path and leave old origin-bound storage behind. A game update may alter its save format. Device cleanup utilities can remove browser site data without treating it as a document.
Storage quota and eviction are additional possibilities. Browsers manage space and may evict data under pressure, especially for origins that are not used regularly. Applications can request persistent storage in supported environments, but the browser decides whether to grant it. A player usually cannot determine from the game interface whether that request was made.
Before clearing data
Do not begin troubleshooting by deleting all cookies and site data. First inspect whether the game has an export, account, recovery code or cloud-save option. Capture non-sensitive settings or progress information that would help identify the save. Never publish authentication tokens or recovery codes.
Use the browser's site-data settings to locate the relevant provider origin. If the problem affects one game, clearing every origin creates unnecessary collateral damage. A hard reload or cache clear is different from deleting cookies, localStorage and IndexedDB, although browser interfaces sometimes combine these options.
If the title loads but shows old assets, clearing cached files may help without deleting storage. Read the confirmation dialog carefully. Browser wording changes, so a guide should describe the category of data rather than promise that a particular button is harmless.
A structured save troubleshooting process
Confirm that you are using the same device, browser and browser profile. Check whether private mode is active. Verify that the external game is being delivered from the expected provider domain. Then determine whether the game offers its own sign-in or synchronization state.
Make a small, reversible change in the game, such as adjusting a non-critical setting, then close and reopen the page normally. If the setting persists, some storage path is functioning. This does not prove that all progress is safe, but it separates a total storage failure from a game-specific save problem.
If storage fails only when the game is embedded, compare the provider's direct experience if the provider offers one and its terms permit the comparison. A difference can point to third-party storage restrictions. Do not weaken global browser privacy settings merely to preserve one game without understanding the tradeoff.
Storage and consent on Spinappy
Spinappy stores one local value named spinappy_game_consent_v1 to remember whether external Playgama frames may load. That value is a site preference, not game progress. Rejecting external games prevents the iframe from loading and therefore prevents that iframe from accessing its normal runtime storage during that visit.
When advertising is eventually enabled, advertising consent will be handled separately through a Google-certified consent platform. The game preference is deliberately not presented as consent for Google advertising. Keeping those purposes separate makes the choice easier to understand.
Reporting a save problem responsibly
Provide the game URL, browser name, operating-system family, whether private mode was used, and whether the issue occurred after clearing data or changing devices. State whether the game has its own account. Avoid attaching a full browser profile, cookie database or screenshots containing personal identifiers.
The site publisher can check links and integration behavior, while the game or distribution provider may need to investigate the actual save implementation. A truthful report distinguishes observations from assumptions: “progress was present before browser data was cleared” is useful; “the website deleted my save” requires evidence about which origin and storage category was removed.