Bindlore Privacy Policy

Last updated: September 28, 2026

Core conversion runs in your browser; files are not uploaded to Bindlore.

What we collect

Nothing. Bindlore has no account system and does not send your files, their text, or the files it generates to Bindlore. The core conversion (reading, OCR, splitting into sections, and building your download) runs inside your own browser.

What is stored locally

Your AI settings (provider choice, model, and your own API key, if you enter one) are stored in your browser via chrome.storage.local. They are never sent to Bindlore.

Optional AI extras (off unless you turn them on)

If you add your own OpenAI or Anthropic API key and tick an AI extra (summaries, key insights & glossary, or flashcards), Bindlore sends text excerpts from the book you are converting, together with your key, directly from your browser to the provider you chose (api.openai.com or api.anthropic.com). Bindlore does not see, relay, or store that traffic. The provider processes it under its own terms and privacy policy.

Permissions

storage, to remember your AI settings in your browser (chrome.storage.local).
Host access to api.openai.com and api.anthropic.com, used only for the optional AI extras described above, and only when you turn them on with your own key.

Your responsibility

Bindlore is a tool for converting DRM-free files you have the right to use, or public-domain works, for your personal use. Owning a copy of a book does not by itself give you every right to process it. You are responsible for having the rights to any file you convert. Bindlore refuses DRM-protected files and does not remove copy protection.

Contact

Questions: info@agencycrusade.com