How local processing works

A Kitolune page is a set of static files. Your browser downloads them, and the tool then runs on your device. There is no application server that receives your document and no account to sign in to.

What happens when you choose a file

1. Your browser reads the file into memory. Nothing is sent when you choose it.
2. PDF work runs in a Web Worker, a background thread in the same tab. Worker files are served with a policy that blocks their network connections.
3. The result is created in the browser and stays there until you select Download. The original file is not changed.

What still uses the network

• The first visit downloads the application from this site.
• Some tools need a larger engine, such as the PDF Studio pack or the optional on-device AI model. These download from this site when needed. They are files coming to you, not documents leaving you.
• The host can log your IP address and the public file paths your browser requests.

How to check this yourself

Finish offline setup, turn off your Wi-Fi, and run a tool. It keeps working, because the work happens on your device.

Open your browser's developer tools, go to the Network tab, and run a tool. You will see downloads of the site's own files. You should not see a request carrying your document.

What local processing cannot protect against

• Anything else with access to your device or browser, such as an extension or malware, may be able to see an open file.
• Files you choose to save with “Save session on this device” are stored unencrypted in this browser profile.
• Splitting or extracting pages does not sanitize a document. Hidden data in copied pages can remain.
• Limits differ by device. Large files can run out of browser memory.

How to merge PDFs without uploading them · Read the privacy page · Offline setup