Privacy Policy

Effective: October 22, 2026 / Updated: October 23, 2026 (added connecting with OpenRouter)

This page explains what data Harie (the web editor, Chrome extension, desktop app and MCP server) handles. Harie is open-source software developed by an individual, and its source code is available on GitHub.

The developer receives no data

Harie has no servers run by the developer. The developer never receives your images, annotations, usage records or device information. There are no accounts, analytics, ads or tracking cookies.

Data stored on your device

• Images and annotations live only in the files (JPEG / PNG) you save.
• The Chrome extension temporarily keeps the captured image, and a list of element positions and text on that page, inside the extension (IndexedDB) to hand them to the editor page. Entries older than 24 hours are deleted the next time you capture. The page element information is never written into saved files. Password field values are never read.
• Your display language, drawing settings such as line width, and the API key for the AI features (an Anthropic key, or the key issued when you connect with OpenRouter) are stored only in that browser's (or the extension's) localStorage.

Data sent outside your device

The AI features (annotation suggestions and personal-data detection) are optional and work only after you register your own Anthropic API key or, in the web version, connect your own OpenRouter account. When you press the button, Harie shows where the data will go, asks for your consent, and then sends the image directly to Anthropic's Claude API (or, when connected with OpenRouter, to Anthropic's Claude through OpenRouter). For images captured with the Chrome extension, the list of element positions and text on the page is sent along with it. That data is handled under your agreement with Anthropic (and OpenRouter, when connected with it), Anthropic's Privacy Policy and OpenRouter's Privacy Policy. It never passes through the developer.

When you connect with OpenRouter, the temporary code you receive on returning from OpenRouter's authorization page is sent from your browser to OpenRouter and exchanged for a key. That key is also stored only in your browser and is never sent to the developer.

If you don't use the AI features, Harie does not send images or page content anywhere.

Chrome extension permissions

• activeTab: to capture only the tab where you pressed the toolbar button or shortcut, and only at that moment. No standing site access is requested at install.
• scripting: to add, each time, the overlay for choosing a region or element and the code that reads element positions and text on the tab you pressed it on.
• downloads: to save the annotated image to your downloads folder.
• Optional site access: requested only when you turn on "Show an edit button on images" or "Show copy buttons for text on images" in the popup. It covers all sites because images are often served from other domains. Buttons appear only on the sites you list (all sites if none), and the access is used only to read Harie images on the page so you can copy their notes or open them in the extension's editor. Images read this way are sent nowhere. Turning the option off gives the permission back.

The use of information received by the Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is never sold to third parties or used for anything other than the purposes described above.

About this website

This website and the web editor are served by GitHub Pages. Access logs are handled by GitHub under the GitHub General Privacy Statement. The introduction pages (including this one) load fonts from Google Fonts. The web editor does not load fonts from external services.

Changes and contact

If this policy changes, this page will be updated, and the change history can be checked in the GitHub repository. For questions, please open an issue on GitHub Issues.