JotDrop is a Chrome extension that clips the current browser tab into a locally-running Obsidian instance. This page explains exactly what the extension does and does not do with your data.
JotDrop never contacts any external server, cloud service, or API outside your own device. There is no analytics, no telemetry, no crash reporting, and no advertising of any kind.
When you trigger a clip, the extension reads:
This information is read on demand only - not continuously, not in the background.
JotDrop can store two values in chrome.storage.local, and both are optional:
If you never configure a token and port, nothing is stored. chrome.storage.local is stored only on this device and is never synced to your Google account or any remote service. No other data is ever written to storage.
Your clipped data travels over two possible local transports - it never leaves your device:
http://127.0.0.1 (your own computer) on the port you configured, authenticated with the bearer token. The request is received by the JotDrop companion plugin running inside your local Obsidian installation.obsidian://jotdrop-clip protocol URL that is handled directly by the JotDrop plugin in your local Obsidian installation. This URI is processed by your operating system and Obsidian on your own computer; the bearer token is never included in it.JotDrop shares no data with any third party, period. There are no embedded SDKs, no tracking pixels, no external scripts.
The extension requests only the permissions it needs:
chrome.storage.localhttp://127.0.0.1/*, http://localhost/*) - to send clipped data only to the JotDrop plugin running on this computerJotDrop is open source under the MIT license. You can inspect every line of code to verify these claims. The source is available at the project repository linked from the Chrome Web Store listing.
Questions or concerns? Reach out to DiexarLabs at eric@diexar.com or open an issue on the project repository.