Backup and Data Locations

Treat Sthang data as sensitive.

Before you begin

Close Sthang and stop active work. Prepare encrypted storage that is not a public repository, shared support folder, or unencrypted removable drive.

Per-user locations

Application configuration, UI state, attempt history, and duplicate-prevention records are stored under:

%LOCALAPPDATA%\co.sthang.app\

License activation remains under:

%LOCALAPPDATA%\Sthang\

Wallet folders may live elsewhere. Sthang preserves their references but does not automatically copy the external wallet folders into its application-data backup.

Create the backup

1. Copy both Sthang per-user directories to encrypted storage.
2. Copy every external wallet folder referenced by Sthang.
3. Keep bot_config.json and .bot_master.key together. A mismatched pair can make encrypted configuration unrecoverable.
4. Preserve the attempt history and duplicate-prevention records with the rest of the application-data directory.
5. Test that the backup can be listed and read, without opening or sharing secret contents.

Normal installer upgrades and signed in-app updates preserve these locations. On first launch after an upgrade, Sthang may copy recognized older data into the stable location. It does not overwrite an existing destination when the sources conflict.

Completion check

Confirm that both per-user directories and every referenced external wallet folder appear in the encrypted backup. Verify that the backup can be listed and read, without opening, printing, or sharing secret contents.

Stop and get help

Stop if one of the paired configuration files is missing, two source locations conflict, or a destination already contains different data. Do not merge, overwrite, or delete either copy. Contact the Sthang owner through the private support channel without sending the files or sensitive paths.