Live measurement
0 bytes of your file uploaded
Verified live in this browser: not a single network request has been made since watching began.
Everything this tab fetched (0)
These are downloads — code, fonts and on-device engines coming to your browser. None of them carries a file body away from it.
Nothing at all has been fetched since watching began. Not one request.
How this works
Your browser keeps its own log of every file a page fetches — the Resource Timing API. This panel reads that log and lists what it finds. On top of it, Omnikit wraps the four ways a page can push data outward (fetch, XMLHttpRequest, sendBeacon and WebSocket) so it can also report the HTTP method and the exact size of anything placed in a request body.
That is why the number above is a measurement rather than a promise. If a tool ever did post your file somewhere, a row would appear here with the method and the byte count, and the panel would turn amber.
What this is not. It is evidence from inside the page, not a formal security audit. It sees this tab only — not browser extensions, not other tabs, not requests your browser or network make on their own. A cross-origin server that does not send a Timing-Allow-Origin header can withhold its size figures, in which case we print “not disclosed” instead of guessing. Requests made before monitoring started are still listed, but their HTTP method is shown as unobserved.
The test you can run yourself: switch off your Wi-Fi, reload a tool you have opened before, and use it. If it still works, the processing was never happening anywhere but on your machine.
Omnikit is a single page, so this record survives moving around the site. Local tools fetch code and models without uploading your file. Server converters send the selected file after you explicitly start the job.
The limits, stated plainly: this reads the tab you are in. It cannot see another tab, a browser extension, or anything your browser does on its own. The record belongs to this page load, so a full refresh throws it away and starts counting again.
Your files
Local tools read and process files in your browser. Closing the tab clears their in-memory files. The two Office-to-PDF tools use server conversion: source files are deleted after completion or failure; downloadable results expire after ten minutes. Interrupted uploads and abandoned files are cleaned on startup and periodically. Job diagnostics never include document contents.
Per-tool labelling
Each tool page carries a processing label: Processed on your device or Server conversion. Public server conversion uses encrypted connections and short-lived, private download credentials. Files are not used for training or exposed publicly.
Opening a file or selecting a workflow never starts an upload automatically. You choose whether to run a server conversion.
Data stored in your browser
Favourites, recently used tools, your local usage counts, saved workflows, your theme choice, tool requests and zero-result searches are stored in your browser’s own storage so the site can be useful to you. They stay on your device and are not sent to the conversion service. Clearing site data in your browser removes all of it.
Reliability metrics and advertising
Omnikit may ask for permission to collect anonymous first-party reliability metrics. If you allow it, we receive coarse page views, tool opens and completion or error outcomes so the private operations dashboard can show what is working. Reliability metrics do not include your files, filenames, file contents, account details or a cross-site tracking identifier. Choosing “Keep local only” leaves those diagnostics in this browser.
Google AdSense / Auto ads is loaded site-wide so the free catalogue can be supported without accounts, paywalls or limits. Depending on your region, browser and Google’s ad settings, Google may use cookies or similar technologies to serve or measure advertising. The Privacy Monitor lists those advertising requests as Google ads, separately from file-processing requests. Omnikit does not send your files to AdSense.