Native PowerPoint Doc Editor is an Obsidian community plugin. This policy describes what information the plugin handles, why, and your choices. It applies to the plugin software distributed through Obsidian's community catalog or manual installation in your vault.
Last updated: June 22, 2026.
The plugin is local-first. It does not operate a server account for you and does not collect profile details or usage analytics.
Information the plugin may store or process on your device includes:
- Vault documents you open, edit, or save (DOCX, PPTX, and related formats).
- Plugin settings you configure in Obsidian (for example editor toggles, optional DOCX search indexing, and diagnostics preferences).
- Optional local caches, such as the DOCX search index file when you enable that feature.
- Recovery copies written locally if a PowerPoint save fails or autosave is disabled.
- Files you choose through system pickers when importing fonts or inserting images; only the content needed for your document is used.
- Debug diagnostics you explicitly copy to the clipboard when developer logging is enabled.
We do not ask you to create an account to use this plugin.
We use the information above only to:
- Open, render, edit, search, save, and export your documents inside Obsidian.
- Remember your plugin settings between sessions.
- Provide optional features you turn on (such as vault-wide DOCX search).
- Help you recover from failed saves when recovery behavior applies.
- Show diagnostics you request for troubleshooting.
We do not use your vault contents for advertising or profiling.
- No telemetry or analytics. The plugin does not phone home or embed analytics SDKs.
- No advertising. The plugin does not load ad scripts or remote UI content.
- No cookies. The plugin does not set browser cookies; Obsidian manages its own application data separately.
We do not sell or share your personal information with third parties for their own purposes.
Your data stays on your device except when you choose an action that leaves the vault, for example:
- Opening a hyperlink inside a document (handled by Obsidian or your operating system).
- Following outbound links shown in settings (for example GitHub issue reporting).
- Exporting a DOCX to PDF when the document references remote image URLs (your browser may fetch those URLs to render the export).
The plugin does not upload vault contents to our servers as part of normal editing, search, save, or export.
Data retention is local-first and under your control:
- Edited documents remain in your vault until you change or delete them.
- Plugin settings persist until you reset or uninstall the plugin.
- Optional search index data remains until you disable indexing or delete the index file.
- Debug log files are written only when a developer hot-reload marker is present; otherwise logs stay in memory and the developer console.
Because processing happens on your device:
- Access your documents and plugin data through Obsidian and your vault folder.
- Delete documents, index files, recovery copies, or plugin data at any time using Obsidian or your file manager.
- Uninstall the plugin to remove its settings from Obsidian's plugin storage.
- Disable optional features (such as DOCX search indexing) in plugin settings.
You may request a copy of information we hold only if you contact us about support for this open-source project; we do not maintain a separate cloud copy of your vault.
We do not sell your personal information. We do not share your information for cross-context behavioral advertising.
For privacy questions or support about this plugin, open an issue on the project repository or contact the author through GitHub: