Your data & API keys
This page explains where Pyre stores data, how keys are handled, and what happens during backup and sync.
Where data lives
| Data | Where it lives |
|---|---|
| Characters, chats, personas, lorebooks, presets, regex rules, settings, Creator drafts | App-private local storage |
| Avatars, gallery images, attachments, backgrounds | App-private local storage, content-addressed where sync uses it |
| API keys | OS-secure storage on native apps |
| Browser/PWA provider keys | Nowhere; the browser stores no provider keys |
| Sync traffic | Between devices/hubs you paired |
There is no Pyre cloud copy.
API keys
When you save a provider on a native app, Pyre separates the key from the main JSON store and writes it to the platform secret store. On startup, it rehydrates keys in memory so the provider can be used.
Normal backups exclude keys. To include keys, you must include the Connections category and confirm the warning. A keys-included backup contains secrets in plaintext inside that file.
Restore behavior
If a backup contains provider keys, Pyre asks whether to use the backup keys or keep the current device's keys. Restored keys are migrated back into OS-secure storage.
Key sync
Provider selections can sync as settings. Provider keys sync only when you explicitly enable encrypted key sync, and browser/PWA clients are excluded by design.
Wiping data
Use Backup & restore for factory reset. Pyre writes a safety backup first and requires typed confirmation before clearing local data.
Uninstalling the app removes the app sandbox according to the platform's normal rules.