Where data lives

Zyper AIO splits state across two roots. Sensitive files go to AppData (encrypted); logs sit next to the .exe so you can grab them for bug reports.

AppData root (encrypted)

%LOCALAPPDATA%\zyper-suite\data\

File	What it holds
`wallets.dat`	DPAPI-encrypted: group / name / private key per wallet.
`rpc.dat`	DPAPI-encrypted: RPC endpoint list per chain (URLs contain auth tokens).
`proxies.dat`	DPAPI-encrypted: proxy list (host:port:user:pass).
`accounts.dat`	DPAPI-encrypted: burner credentials (Discord/Gmail/X tokens + cookies).
`license.json`	Activation key + cached HWID. Plaintext but useless without server-side binding.
`flashbots.key`	Bundle-signing identity. NOT a wallet key — reputation only.
`tasks.json`	Task groups + task configs (onchain + social).
`nft_deploy_cache.txt`	`contract → deployment block` lookup table. Speeds up enumeration.
`nft_metadata_cache.txt`	`tokenId → name + image URL`.
`disperse.txt`	Optional. Per-chain Disperse contract overrides.

Browser profiles root

%LOCALAPPDATA%\zyper-suite\browser\<account-id>\

Per-account headless Chromium profile dirs. Each burner account that uses the browser engine for social tasks gets its own. Cookies + localStorage persist between runs.

If you delete an account, you can also delete its profile dir manually to reclaim disk.

Logs root (next to the `.exe`)

<folder-with-zyper-aio.exe>\logs\
  zyper.log              4 MiB rotation → zyper.log.1
  funds-sessions.log     JSONL, same rotation

These are intentionally outside AppData so you can zip the folder and hand it off in a bug report without digging into hidden directories.

DPAPI in plain terms

Windows DPAPI seals files with a key derived from your Windows user account

machine. Decrypting requires the same user on the same machine. There is no master password and no UI prompt — decryption happens transparently when the app runs as you.

This means:

Copying wallets.dat to a USB and opening on another PC produces gibberish.
Logging in as another Windows user on the same PC produces gibberish.
A different Windows install on the same hardware produces gibberish.

There is no key recovery. If your Windows account is gone, the data is gone. Back up what you care about (wallet keys especially) the old-fashioned way.

Migrating from a pre-v0.15 install

Old builds used <exe-dir>\data\ with plaintext files (e.g., wallets.txt). On first launch of v0.15+, the app migrates everything to the new home and renames the old folder to data.migrated\ so you have a panic-restore copy.

Delete data.migrated\ once you’ve confirmed everything loaded correctly.

Dev overrides

For testing without trampling your real install:

set ZYPER_DATA_DIR=C:\Users\you\.zyper-dev\data
set ZYPER_LOGS_DIR=C:\Users\you\.zyper-dev
zyper-aio.exe