Privacy and boundaries
Where notes live, what reaches a provider and what setup actually authorizes.
Local storage, explicit provider access
Notes remain in the folder you select. The installer does not upload the vault. When a cloud AI reads a note as context, that content may be sent to its provider under that provider’s terms and your application settings.
Local storage does not mean local inference. Choose the files an application can access and avoid storing credentials or other secrets as memory.
Know what you are approving
The setup review lists the planned files and explains the memory behavior requested by startup instructions. Local setup approval is separate from provider login and separate from filesystem permission inside an AI application.
The application can back up its edits to an existing global instruction file. This is not a version-history system for every future AI edit to your notes. Maintain a backup strategy appropriate to your own folder.
Boundaries still being built
Connections can be removed in the desktop panel. This removes tracked integration files, not your notes or the AI provider account. Automatic migration of older skills, coordinated vault switching and policy-controlled writing across all providers remain unfinished.
The companion vision requires separate permission for proactive contact and external actions. Installing a memory skill is not permission to send messages or run background model calls indefinitely.