Scam Report GuideUnderstand it, stop it, report it

KindleForge — Privacy Policy

Privacy policy for the KindleForge — Privacy Policy Chrome extension.

Last updated: 2026-08-10

KindleForge is built with privacy as a first principle. This policy explains what data the extension handles and how it is used.

Short version

documents, images and text happens entirely in your browser via the extension's offscreen document. Your content is not uploaded to any server owned by the extension developer.

SDKs, fingerprinting, advertising identifiers, or third-party trackers.

Data processed and where it goes

Content you convert (e.g. a web page or document)

The content is processed locally on your device inside the extension's offscreen document. The resulting file is then handled in one of two ways, depending on the settings you choose:

1. Send to Kindle by email (via the optional relay). If you enable email delivery, the converted file is sent to the email address you configured (your @kindle.com Send-to-Kindle address) through the email relay service you entered in Settings. The relay receives the file content solely to deliver the email and does not store it. This is the only path where any of your content leaves your device. 2. Download. If you use the Download button, the converted file never leaves your device at all.

Optional AI polish (OpenCode Zen)

If you enable "AI polish" in Settings and provide your own API key, the extension sends a short excerpt of the document (a few sentences, truncated to ~800 characters) plus the title to the OpenCode Zen API endpoint you configured. This is opt-in and off by default. The request is made directly from your browser to OpenCode with your key; the extension developer never sees or stores the content or your key.

Settings you enter

Your Kindle email address, relay URL, auth token, and API key are stored only in the extension's local storage (chrome.storage.local) on your own device. They are never transmitted to the extension developer.

Free-tier usage counter

KindleForge keeps a simple local counter of how many conversions you have used per day for its free-tier (Ko-fi) nudge. This counter never leaves your device.

Permissions explained

The extension requests these permissions to do its job:

| Permission | Why it is needed | |---|---| | activeTab | To detect and convert the page you are currently viewing. | | scripting | To run the content script that extracts web-page articles. | | storage | To save your settings locally. | | contextMenus | To add "Send this page / selection to Kindle" menu items. | | offscreen | To run the converter in a dedicated offscreen document so the service worker stays fast. | | downloads | To save a converted file when you choose "Download". | | tabs | To read the active tab's URL and title for conversion. | | <all_urls> host access | To fetch documents (PDF, Word, etc.) for conversion and to let the content script run on the pages you choose to convert. |

Data retention and deletion

Kindle or downloaded; it is not retained.

needed to transmit the email.

time by removing the extension or clearing extension data in Chrome.

Third-party services

polish and supply your own API key. See their privacy policy for details.

donation page; no data is shared with Ko-fi unless you click through.

Children's privacy

KindleForge is not directed at children under 13 and does not knowingly collect personal information from children.

Contact

For questions about this policy or the extension, please open an issue on the project's GitHub repository.


_This policy is published in the Chrome Web Store listing and is also available in the extension's source repository._