Where Does Cwtch Store Profiles?
Cwtch encrypted profiles in one home folder on desktop, and the password that guards even the list.
Last updated
Cwtch keeps encrypted profiles in ~/.cwtch on Linux, Mac and Windows alike (expanding to the user profile on Windows), overridable anywhere with CWTCH_HOME. Dev builds nest under $CWTCH_HOME/dev so experiments never touch release identities.
Encryption starts before listing: without the password you cannot even enumerate profiles, since keys derive via pbkdf2. Unencrypted profiles use a hardcoded default password, readable by anyone with disk access, so export an encrypted copy from the UI for safekeeping. Android keeps everything in private storage with no browsable path.
Where Cwtch stores this, by platform
~/.cwtch/
Encrypted profile databases. Relocate with CWTCH_HOME; dev builds use $CWTCH_HOME/dev. Export portable encrypted copies from the UI.
%USERPROFILE%\.cwtch\
Same role as Linux (no separate AppData path documented; may vary). Same CWTCH_HOME override and export flow. Android omitted (private storage only).
~/.cwtch/
Same role (no separate Application Support path documented; may vary). Same override and export flow.
Frequently asked questions
How do I back up Cwtch?
Export an encrypted profile copy from the UI and store that file safely. Raw folder copies work only with the password, and unencrypted profiles should be treated as public to disk readers.
Can I run Cwtch experiments without risking my profile?
Yes. Point CWTCH_HOME at a scratch dir for dev builds; they use a dev/ subfolder there, leaving release profiles in the default home untouched.
Notice an outdated path? Let us know.