Clip to Obsidian

Privacy Policy

Last updated: 20 July 2026

Clip to Obsidian is a “bring your own key” (BYOK) browser extension, built so the developer never receives, sees, or stores any of your data. There is no server we operate, and no analytics.

What the extension stores, and where

Your settings are stored locally on your device using the browser’s chrome.storage.local API: your AI provider choice and the API key you paste in, your Obsidian vault name, target folder, save-method preference, and an optional Local REST API key. This data is not transmitted to us.

What is sent, and to whom

When you clip a page:

• The extension reads the page’s text (or a YouTube video’s transcript) locally in your browser.
• That content is sent directly from your browser to the AI provider you selected (Groq, Google Gemini, OpenAI, Anthropic, or OpenRouter), authenticated with your own API key, to generate a summary.
• The resulting note is written to your Obsidian vault on your device.

That request is governed by the provider’s own privacy policy. We are not a party to it.

What we collect

Nothing. No backend, no telemetry, no third-party analytics or trackers. The only network requests are to the AI provider you choose and, optionally, to your own local Obsidian server at 127.0.0.1.

Permissions, and why they’re needed

• activeTab / scripting — read the page you explicitly choose to clip.
• storage — save your settings and key on your device.
• clipboardWrite — pass long notes to Obsidian when they exceed a URL’s length.
• downloads — the optional “download .md file” save method.
• notifications — confirm a right-click clip succeeded.
• host permissions — limited to the AI provider API domains and 127.0.0.1. No broad browsing access.

Contact

Questions: sarthakvarchasvi.work@gmail.com

If this policy changes, the “Last updated” date above will change and the new version will be published at this URL.