Skip to content
Pagewise

Privacy & architecture

Your files never leave your device.

Here's exactly how that works, what we can and can't see, and how to verify it yourself.

There is no server that handles files

Pagewise is a static website: HTML, CSS and JavaScript files served from a CDN (Cloudflare Pages). There are no API routes, no upload endpoints, no database and no file storage. There is nothing on our side that could receive a document, even by mistake.

Processing happens in your browser

When you choose a file, your browser reads it into memory using the standard File API. PDF editing (merge, split, rotate, compress, watermark, page numbers) is done by pdf-lib running inside a Web Worker — a background thread on your device. Page previews and PDF-to-image conversion use PDF.js, also running locally.

Results are created as in-memory Blobs and downloaded directly from your browser. When you press “Start again” or leave the page, those object URLs are revoked and the worker is shut down so the memory can be freed.

Enforced by the browser, not just promised

Every page is served with a Content Security Policy that includes connect-src 'self'. That instructs your browser to block any script on the page from opening connections to other servers. Same-origin requests only fetch our own static code files.

We don't use localStorage, sessionStorage, IndexedDB or Cache Storage for documents. Nothing is persisted after you close the tab.

What we can see

Like any website, our host (Cloudflare) receives standard request logs when your browser downloads our pages: IP address, user agent, the URL requested. These never include file names or contents, because files are never sent. We don't load third-party analytics, advertising, fonts or error-reporting scripts.

Verify it yourself

  1. Open your browser's developer tools (F12, or ⌥⌘I on Mac) and select the Network tab.
  2. Use any tool on a PDF. You'll see no requests carrying your file — at most, requests for our own JavaScript files.
  3. Or: load a tool page, turn off Wi-Fi, then process a file. It still works.

Limits we're honest about

Local processing means your device does the work. Very large files can be slow or run out of memory, especially on phones. Encrypted PDFs must be unlocked before most tools can open them. Password protection and unlocking are not yet available.