Select to Note

What the extension accesses

The extension reads only the web page content that the user actively selects by clicking an element or dragging a rectangle.

It may include visible text, links, image URLs, the current page title, the current page URL, and the capture time.

How data is used

The selected content is converted into Markdown and sent to a local HTTP endpoint on 127.0.0.1 or localhost so the Obsidian companion plugin on the same device can append it to a note chosen by the user.

If the user enables translation, selected text is sent only to the translation engine configured by the user. Supported options include the browser built-in Translator API, Baidu Translate, Microsoft Azure Translator, Google Cloud Translation, and an OpenAI-compatible LLM endpoint.

What the developer collects

The developer does not operate a remote server for this extension and does not collect, store, sell, or share the selected content through a developer-controlled backend service.

Local storage

The extension stores local settings such as the receiver endpoint and shared token in the browser's extension storage so the browser extension and Obsidian plugin can communicate.

Authentication

Communication with the local Obsidian receiver uses a shared token that is sent in the Authorization header. The token is stored locally by the user in the extension and the Obsidian plugin.

Third parties

Select to Note does not send the selected content to advertising networks, analytics providers, or other third-party cloud services by default.

Translation is off by default. Cloud translation providers receive selected text only after the user enables translation, chooses a cloud engine, and enters their own provider credentials. Custom LLM endpoints are controlled by the user.

User control

The user decides when to start selection, what content to select, what local endpoint to use, what token to configure, and whether to enable translation.

Contact

Project repository: https://github.com/TYzzt/select2obsidian