Files are processed in your browser
The four tools do not upload selected file contents to a ToolkitRack processing server. Detection reads up to 4 KiB from each end of a file; image tools decode the complete image. File names appear locally in results, but custom analytics events do not send names, contents, file paths or Blob URLs.
Local processing still involves network requests
A first visit downloads pages, models and WebAssembly engines. The site uses Google Analytics (G-H6XEQCM3YQ) for page and tool usage and may use cookies; the browser sends analytics requests to Google. Hosting and network services may also keep ordinary access logs. This page does not claim zero analytics or zero logs.
What tool events contain
Events record starts, successes, failures, cancellations and download triggers. Parameters are limited to the tool, page language, input/output format categories, elapsed-time buckets, fixed error categories and single-file/ZIP download type. Raw exception text is excluded. A download click does not prove a file was saved to disk.
Offline storage and clearing it
A Service Worker caches program files, models and engines. Local storage remembers the chosen language. Selected files are not added to the site offline cache. Offline use requires the ready badge and a cache that has not been evicted. Clearing this site’s browsing data removes its cache and language preference.
Check it yourself
Open the browser developer tools Network panel and process a non-sensitive test file. Distinguish program downloads and Google analytics requests from file uploads. Do not publish debugging records containing private names. After the offline badge is ready, disconnect and reopen a cached tool to test local processing.