Guide
Cloud Saves
One code, every device. Your saves, encrypted, synced.
Quick facts
- Added in
- v0.2.8
- Opt-in
- Off by default. Settings toggle.
- Free
- Auto-Save + Slot 1 synced
- Patreon
- All slots synced
- The code
- Six words. Write it down. It cannot be recovered.
Cloud Saves keep your progress in sync between devices: browser, Windows, Android, any mix. It is completely optional and off by default. Turn it on in Settings, confirm the consent dialog, and either create a new sync code or enter the code from another device.
If you only play on one device, the feature still earns its keep: browsers can and do silently delete locally stored game data (this is the number one cause of lost saves on itch.io), and a cloud copy survives that. See Faq for the full story on disappearing browser saves.
The sync code
When you enable cloud sync for the first time, the game generates a sync code: six random English words, something like tiger-velvet-anchor-mango-frost-cabin. That code is your entire cloud identity. There is no account, no email, no password, just the code.
Three things to understand about it:
- You cannot pick your own code. The code doubles as the encryption key for your saves, so it has to be random. A code you chose yourself could be guessed, and anyone who guesses a code can download and decrypt the saves behind it.
- Write it down when it is shown. The game shows the new code once in a dialog and tells you to save it. On a device that already has the code you can re-reveal it in Settings (it is stored on the device), plus there are Copy and “Save as file” buttons. But if you lose all your devices and you never wrote the code down, it is gone.
- A lost code means lost cloud saves. This is by design. The saves on the server are encrypted with your code, and the server never sees the code itself. Nobody, including the developer, can reset it, look it up, or decrypt your saves without it. Your local saves are never affected either way.
What “zero-knowledge” means here
Your saves are encrypted on your device before anything is uploaded. The server (in Germany, EU) only ever stores an unreadable encrypted blob, a slot number, a size, and a timestamp. No name, no email, no account, and no way to read what is inside. Even if the server were stolen outright, your saves would stay private. The flip side is the rule above: only your code can decrypt them, so the code is genuinely irreplaceable.
Free vs Patreon
Everyone gets cloud sync. The difference is how many slots ride along:
- Free: the Auto-Save and one manual slot (Slot 1) sync to the cloud. That manual slot is your anchor: a save the autosave can never overwrite, safe from browser cleanup.
- Patreon: all save slots sync (Auto-Save plus all six manual slots).
The slot list in the save menu shows a badge per slot: “Cloud saved” or “Local only”.
Switching to a new device
- Install or open the game on the new device.
- Settings, enable Cloud Save Sync, confirm the consent dialog.
- Instead of creating a new code, use “Enter code from another device” and type your six words. The input is forgiving: any separator works, capitalization does not matter, and each word is checked against the wordlist as you type, so typos are caught immediately.
- Confirm the import dialog. The cloud copies are downloaded into the synced slots on this device, replacing whatever was there. Other slots are untouched.
Re-entering your own code on a device you already play on works the same way and doubles as the recovery path: it pulls the cloud versions back into the synced slots.
How syncing behaves day to day
- While playing, the game saves locally every turn exactly as before. Cloud uploads happen in the background: manual saves push immediately, the autosave is bundled up and pushed every couple of minutes, and the game flushes a final push when you quit or close the tab.
- On startup, the game compares each synced slot with its cloud copy and the newest version wins. Empty local slots are filled from the cloud. If you played offline, that progress is not lost; it gets pushed up on the next sync.
- Deleting a synced slot deletes its cloud copy too. Otherwise the next startup would just restore it. The confirmation dialog tells you when a cloud copy exists.
What syncs and what does not
The full save payload travels: story progress, inventory, character data, statistics, gallery unlocks, perk selections, and achievements (achievements merge additively into the device, so loading an older save never takes earned achievements away).
Device settings intentionally do not sync: language, text scale, and audio settings stay per device.
Retention and deletion
- Inactive saves are purged after 12 months. If a save has not been updated for a year, the server deletes it. Your code stays valid forever though: the next time you sync with it, fresh copies are simply uploaded again.
- “Delete cloud saves” in Settings immediately and permanently removes everything stored on the server for your code. Local saves are not affected. This cannot be undone.
- Turning the sync toggle off asks whether you also want to delete the server copies. Either way, local play continues unchanged.
Tips and gotchas
- Write the code down somewhere outside the game. Password manager, notes app, a piece of paper. The “Save as file” button gives you a small text file you can stash with your backups.
- Generating a new code abandons the old cloud saves. You can create a fresh code at any time, but saves uploaded under the old code stay encrypted with the old code. Use “Delete cloud saves” first if you want them gone immediately, otherwise they age out via the 12-month purge.
- Cloud sync is a complement to JSON export, not a replacement. The Export buttons in Settings still produce a save file you fully control. For maximum safety, do both.
- Free players: use Slot 1 deliberately. It is your one synced manual slot, so treat it as the “this run matters” save.
Related
- Faq for the short answers on save loss, platforms, and where to play.
- Getting Started if you are brand new.
- Patreon Vs Free for what else the Patreon build includes.
Comments
Patreon supporters can post. Public can read. Posts show under an anonymous handle (e.g. Quiet Owl 423) derived from your account, your real Patreon name stays hidden.