Plain-language privacy

Your book is yours.
Your key is yours.

Leafmark is a static, local-first reader. It has no Leafmark account system, database, advertising tracker, or server that stores your uploaded book or API key.

Effective August 29, 2026

01Books stay local

PDF and EPUB text is extracted in your browser. Excerpt checkpoints are saved only in browser storage on this device.

02Keys stay temporary

Your key is held only in this tab's memory and disappears on refresh or close.

03You choose the provider

When enabled, Leafmark's built-in NVIDIA connection uses a disclosed, stateless relay because NVIDIA's API blocks browsers.

1. What Leafmark processes

When you choose a PDF or EPUB, Leafmark reads its selectable text in your browser to make a reading guide. The file is not uploaded to a Leafmark server. You should only use books you are legally allowed to access and process.

As each AI excerpt finishes, Leafmark stores its validated summary ledger in this browser's IndexedDB storage. This allows a later retry or refresh to restore completed excerpts without sending them again. These checkpoints may contain short generated summaries and page references, but not your API key or the uploaded book file. Clearing this site's browser data removes them.

2. How API keys are handled

Entering a key is optional. Leafmark keeps it in the current browser tab's memory by default; it is not written into the site, exported with a guide, or intentionally sent to analytics or logging services. Refreshing or closing the tab removes it.

When you test a connection or use an AI model, the browser sends the key to the provider or custom endpoint you selected so that service can authenticate the request. NVIDIA is the exception: its API blocks direct browser requests, so NVIDIA keys pass transiently through Leafmark's relay. Leafmark does not store or retain them. Use a dedicated, revocable key with a spending limit whenever your provider supports those controls.

3. When an AI provider receives content

Leafmark asks for explicit consent before enabling AI reading. Once enabled, the selected service may receive your API key, book excerpts needed for the request, model settings, and ordinary network metadata. That provider's own terms, privacy practices, retention rules, training policies, and charges apply. Leafmark does not control them.

For AI reading, Leafmark sends bounded, source-labeled excerpts rather than the uploaded file itself. The provider classifies those excerpts into a content ledger; Leafmark validates the returned source IDs and assembles the reading depths locally.

4. NVIDIA relay

When the built-in NVIDIA connection is enabled and you select it, your API key, bounded book excerpts, model settings, and ordinary network metadata pass through a Leafmark-operated Cloudflare Worker before reaching NVIDIA. The relay has no application API key, database, cache, analytics code, or intentional request-content logging. It holds each bounded request only long enough to forward it and does not store it.

Cloudflare necessarily processes the transient request while operating the relay under its Privacy Policy. If you do not want to use Leafmark's relay, connect a local NIM or a relay you control under Custom.

5. Custom endpoints

If you enter a custom OpenAI-compatible endpoint, requests go to that address. Leafmark permits HTTPS endpoints and local HTTP addresses. You are responsible for trusting the operator, reviewing its policy, and confirming that the endpoint is appropriate for the book you are processing.

6. Hosting, cookies, and analytics

Leafmark is served through GitHub Pages. GitHub may process technical information involved in delivering the site under its General Privacy Statement. Leafmark itself currently uses no advertising cookies, behavioral analytics, or user accounts.

7. Provider policies

Review the policy for the service you connect: Google, Groq, Cerebras, Kimi, or NVIDIA. For any other provider, use the policy published by that provider.

8. Security and changes

No browser application can promise absolute security. A malicious browser extension, compromised device, or untrusted endpoint could expose information displayed or entered in the browser. Keep your browser and device secure, restrict API-key permissions, and revoke a key if you suspect exposure.

If Leafmark later adds optional saved settings, analytics, accounts, or server-side processing, this page will be updated before those features are treated as part of the normal service.

9. Questions

For a privacy question or correction, open an issue in the Leafmark GitHub repository. Issues are public, so do not include an API key, private book text, or other sensitive information.