Protect your data.
Mnémosyne functions as a local storage solution on your Mac. Control over your data remains within your work environment, but this also means you need to secure access to the application and maintain an appropriate backup strategy.
Your data remains on your Mac.
Mnémosyne organizes its data in a local vault associated with your work environment.
This architecture allows you to maintain control over your folders, tasks, documents, and notes in the environment where you work.
However, privacy does not depend solely on where your data is stored: your Mac, access to the app, and your backups must also be properly protected.
Local Storage and Backup are not the same thing.
Where you work
The vault contains the data that Mnémosyne uses on a daily basis on your Mac.
It is your primary work environment.
This allows you to recover
A backup is a copy intended to protect your work or to enable recovery if the main storage location encounters a problem.
The guide therefore recommends a policy of regular backups, even when data is stored locally.
A hardware failure, user error, or a major reorganization may justify keeping a separate copy of your work.
Lock the app when you're away.
The guide recommends using auto-lock when you are working in a shared environment.
The appropriate timeframe depends on how you use it: a personal computer in a private setting does not pose the same level of exposure as a Mac used in a shared office.
The goal is not to impose more restrictions, but to prevent a safe containing business information from remaining accessible unnecessarily.
See the Settings guide →Plan for Recovery before you need it.
The guide recommends a regular backup strategy to protect your work, prepare for switching to a new Mac, or be able to restore your data after a hardware issue.
Make regular backups when the information in the vault is critical to your business.
If you keep an export or a working archive, make sure it matches what you want to preserve.
Use simple names to distinguish between vaults and different backup versions.
A backup should allow you to recover your work when the main storage location can no longer be used.
Some moments are worth an additional copy.
Before making a major change
The guide recommends making a copy before a major reorganization of your trunk or your data.
Before switching to a new Mac
A backup or export can be used to prepare for moving your vault to another environment.
When the loss is hard to accept
The more important the information stored in a safe, the more important it is to review its recovery strategy.
Securing a Safe or plan your trip.
The V1.3 guide recommends using the backup or export features when you want to secure a vault or prepare for a migration.
Before treating an export as a working archive, make sure it contains the items you want to preserve.
The V1.3 guide confirms the use of the save and export functions, but does not document their interface in sufficient detail to specify a precise sequence of button clicks here.
A backup is more useful when its restoration has been verified.
For a critical issue, the guide recommends testing the rollback in a test environment.
This precaution allows you to verify a backup without having to rely on it for the first time at the very moment an incident occurs.
The level of control to be applied naturally depends on the significance of the data in question.
A simple name avoids poor restorations.
The guide recommends a simple naming convention that makes it possible to distinguish between the relevant folder and the different backup versions.
Use a descriptive name, along with a date or version identifier when multiple backups need to be retained.
Delete with caution.
The guide recommends moving an item to the Recycle Bin only when you are certain that it is no longer needed.
In an application designed to preserve context, past information can still help understand a case, an assignment, or a decision.
Before deleting, make sure the item no longer provides any useful context and is not intended to be kept in your work history.
Verify that this is the correct item, that it is no longer needed for tracking, and that its removal will not take away any important information from the context of the file.
When a major reorganization is planned, first back up the vault.
Safety is also important through a coherent organizational structure.
The guide explicitly links data retention to proper organization of the safe.
Misfiled files, duplicates, or documents placed in the wrong context increase the risk of losing track of things, even when the files themselves are still there.
Import it, then immediately link it to the correct client file and the corresponding assignment, if necessary.
Add a short note when the information should remain within the context of the file.
Check the items you've added and sort through what still needs to be organized.
Check your open tasks and any notes that are still pending to reduce the buildup of items without a clear context.
A question about Your data?
Yes. The V1.3 guide describes Mnémosyne as a local vault that runs on your Mac.
No. The guide recommends a regular backup plan in addition to the safe used on a daily basis.
Make a backup copy before making a major change to the organization.
Use the built-in backup or export features to secure the vault and prepare for a migration.
The guide recommends testing the recovery process in a test environment when the level of risk warrants it.
Move it to the Trash only when you are certain that it is no longer needed for your work or in the context of the file.
Continue to protect your workspace.
Your Help Center is now full.
Check out the guides on client files, assignments, documents, notes, context, search, activities, settings, and best practices for Mnémosyne.
Back to the Help Center →A problem with Your trunk?
If a problem related to your data, a backup, or the configuration persists after performing the recommended checks, contact KharonBridge support.
Contact support
