Your files stay in your browser

Private File Tools processes selected files locally in your browser. The application does not send file names, file contents, pasted document text, or generated output to a conversion server.

Anonymous usage events

The site sends a small first-party event to /api/event. Its application payload contains only the current site path and one event name: page view, tool start, success, failure, or download. It contains no account ID, advertising ID, file name, file size, or file contents. These counters help find broken tools and understand which tools are useful.

Cookies, accounts, and advertising

The public tools do not require an account and do not set advertising or cross-site tracking cookies. The private statistics page stores its administrator token in that tab’s session storage so it can reload the dashboard; public visitors do not receive or need that token.

Hosting data

Like other websites, requests for pages, scripts, and the anonymous event endpoint pass through the hosting and security provider, Cloudflare. Standard request metadata may therefore be processed by Cloudflare for delivery, abuse prevention, and security. That infrastructure data is separate from the application event payload described above.

Your choices

You can load a tool, disconnect from the network, and then perform supported local operations. Media tools may need to download their WebAssembly engine before going offline. You can also block /api/event; conversion does not depend on analytics.