Local Data & Exports
Where Zyper stores data, what is encrypted, and how plaintext exports differ from backups.
Zyper is local-first. Wallets, accounts, tasks, settings, caches, and browser profiles live on the computer running the app rather than in a Zyper cloud account.
Storage locations#
| Data | Windows | macOS |
|---|---|---|
| App data | %LOCALAPPDATA%\zyper-suite\data | ~/Library/Application Support/Zyper AIO/data |
| Browser profiles | %LOCALAPPDATA%\zyper-suite\browser-profiles | ~/Library/Application Support/Zyper AIO/browser-profiles |
| Logs | logs beside the .exe | ~/Library/Logs/Zyper AIO/logs |
The sensitive stores wallets.dat, solana_wallets.dat, bitcoin_wallets.dat, rpc.dat, proxies.dat, and accounts.dat are encrypted at rest. Windows uses user-and-machine-bound DPAPI. macOS uses AES-256-GCM with a device-only master key stored in Keychain.
Some operational state is intentionally not a secret store, including task/whitelist JSON, caches, logs, PnL presentation files, account authentication status, and browser profiles. Protect the whole user account and disk, not only the encrypted .dat files.
CSV export versus backup#
Settings → Data Export exports one dataset—wallets, accounts, RPCs, or proxies—as plaintext CSV for manual use. Credentials and private keys in those exports are readable. CSV is not a complete migration or recovery copy.
Use Backup, Restore & Migration for a password-encrypted, multi-dataset archive. Store either kind of export outside shared folders and delete temporary plaintext copies securely.
Local deletion#
Deleting a wallet, group, task, whitelist, or browser profile updates local state. There is no cloud recycle bin. Back up before bulk deletion and verify the file exists somewhere independent of the app-data directory.
Logs can contain URLs, addresses, task errors, and operational context. Review them before sharing and send only the relevant time window when asking for support.