Obsidian

Obsidian says desktop and mobile vault data is saved locally on the device and is not sent to Obsidian servers by default.

Users can avoid Obsidian-hosted services entirely and keep private notes outside vendor AI pipelines.

Optional Sync and Publish are separate choices rather than mandatory note-processing defaults.

Community plugins and third-party AI add-ons can still create their own note-processing and training exposures.

Local vaults do not have to be shared with Obsidian at all when users stay off optional cloud features.

Users decide whether to enable Sync, Publish, and community plugins that move note data beyond the local device.

The policy documents security measures and optional service boundaries instead of treating every vault as always-online content.

Once users enable Sync, Publish, plugins, or outside integrations, vault content may be processed by those additional services.

A local vault avoids routine cloud analytics over note content.

The core product posture is far less tracking-heavy than ordinary cloud collaboration suites.

Users can separate sensitive note-taking from the website, account, and plugin ecosystems when they want a stricter setup.

Website, account, Sync, Publish, and plugin ecosystems still introduce some ordinary analytics and operational tracking.

Users can keep vault data on their own devices and delete it directly without waiting on vendor retention cycles.

The policy says expired Sync or Publish subscription data remains on servers for one month and is then deleted permanently.

Users can maintain their own offline copies and exports rather than depending entirely on vendor retention behavior.

Optional cloud services and external plugins can impose separate retention behavior outside the local vault model.

Users choose where the vault lives and can keep it entirely local.

Sync, Publish, and plugin installation are all optional user decisions instead of hardwired defaults.

Plain-file exports and local ownership give users a durable exit path.

Privacy can degrade quickly if users install unreviewed plugins or route notes into outside AI services.