No file-processing endpoint
There is no application route designed to receive the selected document or image.
The network boundary, explained
PandaFileKit is a browser-first utility platform: choose a file, perform one useful task, download the result, and leave. The file-processing path begins and ends inside the tab.

The processing path
There is no hidden upload stage between these steps.
A File reference exists only after you choose or drop something into the page. PandaFileKit does not receive a remote URL or upload token.
JavaScript libraries, Canvas, and browser APIs read the bytes in memory and perform the requested operation locally.
The result is exposed through a temporary Blob URL. That URL is revoked when it is no longer required.

Why PandaFileKit exists
“Private” is too vague on its own. PandaFileKit states which server components do not exist and separates file processing from optional publisher services.
There is no application route designed to receive the selected document or image.
PandaFileKit has no upload bucket, conversion queue, or database record for file contents.
Outputs report real byte sizes and explicit trade-offs instead of claiming impossible compression.
Each route performs one defined task without an account, dashboard, or setup workflow.
Honest browser limits
Large rasterized PDFs, expanded archives, and high-resolution images may use several times their compressed size in memory. Tools enforce practical limits rather than letting a tab fail without context.
Deliberate exclusions
Encrypted archives, password-protected PDFs, proprietary codecs, OCR, and pixel-perfect Office rendering are excluded when a dependable browser implementation is unavailable.
One task, then leave
No account setup and no workspace to maintain afterward.