Clear, local-first clipboard handling
ClipVault is built around local text clipboard workflows. This page explains what the app stores and what users should understand before using backup and restore features.
Clipboard content can be sensitive. Treat exported backups and copied content with the same care you would give any other local data on your machine.
What ClipVault stores
ClipVault can store:
- Clipboard history entries
- Pinned items
- Snippets
- Application settings
- Log files used for troubleshooting
Where data is stored
ClipVault stores its local data inside the user’s local application data area on Windows. That currently includes the app database, settings, and log files.
What backups may include
Backup exports can include clipboard items and settings. If you export a backup, treat that file carefully and only store or share it in places you trust.
What ClipVault does not try to be
ClipVault is not a cloud sync service and is not presented as a password manager. It is a local clipboard tool focused on helping users organize and reuse text more effectively.
User control
Users can already control core behavior such as:
- Whether clipboard monitoring is enabled
- History size limits
- Whether the app stays available in the tray
- Whether to export or restore application data
Logs
ClipVault includes local log files to help with troubleshooting. Users should avoid sharing logs publicly unless they have reviewed them and are comfortable with the contents.
Ongoing improvements
ClipVault continues to improve how it handles sensitive clipboard workflows. As privacy-focused controls expand, this page should be kept in sync with those changes.