← Kadr

Privacy policy

Last updated: 31 August 2026 · applies to the Kadr browser extension

The short version

Kadr has no backend and no analytics. Screenshots, documents and settings stay in the browser on your computer. Nothing is sent anywhere unless you press a button that says it will send something.

What is stored, and where

• Screenshots, documents and style presets — in the browser’s IndexedDB, on this computer. They are removed when you delete them in the library or remove the extension.
• Settings, API keys and tracker tokens — in chrome.storage.local. Deliberately local and not sync: keys must not travel to a cloud account.

What leaves the device, and only when you ask

• An AI action. If you enable AI and enter your own key, the image on the canvas and your prompt go straight to the endpoint you configured — OpenAI, Anthropic, Google, OpenRouter, or a local server. They do not pass through us; we have no server in this path. What that provider does with the data is governed by their terms.
• The local OCR dictionary. The first offline text recognition downloads a language file for Tesseract from tessdata.projectnaptha.com — the only third-party host this extension ever contacts on its own. The request carries no data about you, and nothing about the image leaves the device: recognition itself runs in the browser.
• Sending a shot to an issue tracker. If you configure GitHub, Linear or Jira, the picture, the title, your description and the page context (url, browser, screen size) go to that tracker with your token. Access to the tracker host is requested at that moment, not at install time. Linear hands back a presigned upload url on storage.googleapis.com, so that host is asked for together with it.

What never happens

• No telemetry, no analytics, no crash reporting, no “anonymous usage statistics”.
• No account, no sign-up, no advertising, no third-party trackers.
• No selling or sharing of any data, because none of it reaches us in the first place.

Permissions and why they exist

• activeTab, scripting — read the page you are capturing, at the moment you start a capture.
• storage, unlimitedStorage — keep documents, shots and settings locally.
• downloads — save the exported file.
• clipboardWrite — copy the shot when you press Copy.
• contextMenus — the right-click entry points.
• Host access — optional, one site at a time and always behind a button: reshooting a saved shot, recording a step guide across pages, sending to your issue tracker.

Contact

Questions and reports: open an issue in the repository. The extension is open source — every claim on this page can be checked in the code.

Политика приватности

Обновлено 31 августа 2026 · относится к расширению Kadr