Berd is using a local-first data model that stores conversation history on the user’s device, according to Axen. The design separates chat records from credentials, which are kept in the operating system’s keychain by default.
The approach gives users more direct control over where their conversation data resides. It may also reduce the amount of sensitive information sent to remote systems. However, local storage shifts some security and backup duties to the device owner.
How Berd Stores User Data
Conversation history is saved in the local Goose session database. This means past exchanges remain on the device within the user’s Goose environment.
“Conversation history is stored on the user’s device in the local Goose session database.”
Credentials receive different treatment. Berd places them in the operating system keychain by default, rather than storing them with conversation records.
Keychains are secure storage services built into major operating systems. They typically protect passwords, access tokens, and other secrets through encryption and system access controls.
The separation creates two distinct storage paths:
- Conversation history stays in the local Goose session database.
- Credentials remain in the operating system keychain by default.
Why Local-First Storage Matters
A local-first model treats the user’s device as the main location for data. That differs from services that keep conversation histories primarily on company-operated servers.
Local storage can support privacy by limiting routine transfers of chat records. It can also help users retain access to stored sessions when a remote service is unavailable, depending on Berd’s wider operating requirements.
Yet the model does not remove every security risk. Anyone who gains access to an unlocked device may also gain access to locally stored records. Device encryption, account passwords, software updates, and physical security remain important safeguards.
Local data may also be lost if a device fails or is stolen. The available information does not explain whether Goose offers encrypted backups, data export, synchronization, or recovery tools. Those details would affect how users balance privacy with resilience.
Credentials Receive Added Protection
Keeping credentials in the operating system keychain follows a common security principle: secrets should not be placed in ordinary application databases. Keychains can restrict access and reduce accidental exposure through files, logs, or routine database handling.
The phrase “by default” suggests that this is Berd’s standard configuration. It does not clarify whether users can select another credential store or change related settings.
The effectiveness of the design will depend on its implementation. Important questions include whether conversation records are encrypted at rest, how database permissions are managed, and how deletion works.
Berd’s local-first structure offers a clear privacy benefit: conversation history stays close to the user, while credentials receive protection from the operating system. The next issues to watch are backup options, encryption, synchronization, and secure deletion. Clear documentation on those controls will help users judge whether the model meets their security needs.
Deanna Ritchie is a managing editor at DevX. She has a degree in English Literature. She has written 2000+ articles on getting out of debt and mastering your finances. She has edited over 60,000 articles in her life. She has a passion for helping writers inspire others through their words. Deanna has also been an editor at Entrepreneur Magazine and ReadWrite.
