Privacy Policy

Last updated: October 2026

The short version

Your documents never leave your device. All decoding, page rendering and PDF generation happen locally in your browser. Our servers never receive the files, any page of them, or anything you type into the tool.

What we do NOT collect

• Your .djvu files — they are read by JavaScript and WebAssembly running in your browser tab and are never uploaded.
• Document content — page images, text layers, metadata, and the generated PDF files stay in your browser's memory and are discarded when you close the tab.
• Accounts and cookies — the site has no signup, and it sets no cookies.

What is stored on your device

If you purchase and activate a license, a signed license token, its tier and its activation timestamp are stored in your browser's localStorage (key djvuview_license) so you don't have to re-enter it. An anonymous random ID (key vid) is also kept so we can count unique visitors in our usage statistics — it contains no personal data, and your files never leave the browser. Clear your browser's site data at any time to remove both. Nothing else is persisted.

What is sent over the network

• Page loads. The site is static files served by our hosting provider (Vercel). All JavaScript and WebAssembly libraries are self-hosted on the same domain — no third-party CDN is contacted. Like any web request, the hosting provider may log your IP address and user agent per its own privacy policy.
• Anonymous usage statistics. We use Vercel Web Analytics, which counts page views and referrers without cookies and without collecting any file or personal data.
• Anonymous usage counters. Our server keeps running counts of tool events: a page view happened (with a coarse referrer category), a button was clicked (upload, sample, export, buy, validate), an export happened (page count, DPI, full or capped at the free 3 pages), and client-side error codes (not a DjVu file, file too large, decode failure, export failure) with a short sanitized error message. To count unique visitors and tell free from licensed usage, events carry an anonymous random ID generated and stored only in your browser — only a hash of it reaches our statistics, never the ID itself. These are bare numbers — they never include page content, document metadata, or file names.
• License validation (paid users only). When you enter a license key, the key — and only the key — is sent to our serverless endpoint, which forwards it to Gumroad's license API to confirm validity. No file data is ever attached to this request.
• Checkout (paid users only). If you buy a license, the transaction is handled by Gumroad under their privacy policy. We receive only an order confirmation and your email address for license delivery.
• Feedback you choose to send. The Feedback link opens a form delivered by Web3Forms: only the text you type and, if you fill it in, your reply email address are sent. Never attach or paste your document content — we cannot use it and do not want it.

Data retention

Your documents are never sent to us, so there is nothing for us to retain or delete. Anonymous usage counters (numbers only, as described above) are kept as daily aggregates and lifetime totals. License and order records are retained by Gumroad as required for accounting purposes.

Changes to this policy

If we ever change how data is handled, we will update this page. Any feature that would require sending file content to a server (we have none planned) would be opt-in and clearly marked before it affects you.

Contact

Questions about privacy? Email hello@djvuview.com or reply to your Gumroad receipt.