Where Does Voyager Store Sessions and Settings?
Voyager keeps Lemmy sessions server-side with app settings exportable as JSON. Login state never leaves the device wholesale.
Last updated
Voyager splits identity from preference cleanly. Lemmy accounts hold the data while the app holds UI setup exportable as JSON. Sessions never join the export by design.
The package ID stays constant across Play, F-Droid and GitHub with reproducible signatures easing store switches. Self-hosted web builds stay stateless with server suggestions through environment. Migrate prefs by file and accounts by login.
Where Voyager stores this, by platform
/data/data/app.vger.voyager
Private storage for the verified cross-store package with prefs and sessions inside. Settings JSON export covers UI without logins. Self-hosted web builds configure through environment variables.
Frequently asked questions
How do I move Voyager to a new phone?
Export settings JSON from the bottom of Settings General, which dumps app prefs without login sessions or account-synced options. Import the same file on the new install, then sign back into servers. Reproducible builds ease Play to F-Droid moves.
Does Voyager backup include my logins?
It exports preferences only. Sessions and Lemmy-synced options stay out by design, so accounts sign in fresh everywhere. Keep the JSON for UI setup and expect login work after every migration.
What is the Voyager package name?
Use app.vger.voyager across Play, F-Droid and GitHub releases with matching signatures. Data follows the Lemmy account while prefs stay local. Self-hosted web builds configure suggested servers through environment rather than files.
Notice an outdated path? Let us know.