Your files.
Your browser.
Your business.

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.