Home / How we can say that
How we can say that
Every privacy page on the internet says some version of "we don’t collect your data." This page does something different: it runs a live counter of every request it has actually made, right now, and gives you a real file to test it with — so the claim is something you check, not something you read.
The number below is not a screenshot or a claim — it is a live count of every network request this exact page has made, read from your browser’s own resource-timing log. Pick a file in the box further down and watch the number after it. It will not move.
What this actually proves, and what it does not
This page proves a narrow, specific thing: a file you pick here is read into this browser tab’s own memory and never becomes a network request, because there is no code on this page that could send it anywhere even by accident. It does not, on its own, prove that the full editor at /app/ behaves the same way while you are actively editing a real PDF across many tools and many minutes — that claim is bigger, and it has its own, more complete version of this exact monitor built into the editor itself, showing every request across an entire editing session, not just one page load.
Check the bigger claim yourself, in the real editor
- Open the editor, load a real PDF, and edit it — add a signature, a stamp, redact something, export it.
- Open the Privacy Monitor tab inside the editor’s own side panel while you do. It is the same live request list this page uses, running for as long as you keep the tab open, across everything you do.
- Or skip both and open your own browser’s network tab before you start. It will show exactly what both monitors show, because both are reading the same browser-native log — nothing here depends on you trusting either one.
Why a live page instead of another paragraph
A privacy policy is a promise. A number that updates while you watch, next to a file picker that lets you try to break the promise yourself, is closer to evidence. Nothing about this page's own request count is unique or special — every browser already keeps this log for every page you visit, for its own performance debugging. This page just puts that existing, browser-native record somewhere you can actually see it, instead of asking you to open developer tools yourself to find the same thing.
Straight answers
What is actually being monitored on this page?
The exact same mechanism the editor’s own Privacy Monitor uses: the browser’s built-in PerformanceObserver, reading its own resource-timing log — a record every page in every browser already keeps, that this script only displays rather than creates. It is not this site’s claim about itself; it is the browser reporting on itself, and you can open your own network tab right now and check it says the same thing.
Why does the counter show a few requests, not zero?
Because this page itself had to load — its HTML, its stylesheet, this script. That is the honest, small number you see the moment the page finishes loading, and it stops there permanently. The actual claim was never "nothing is ever requested" — a page has to arrive somehow — it is "nothing about your files is," and that is what the file picker below lets you check directly.
Is the file I pick in the box below actually read?
Yes, genuinely — into this browser tab’s own memory, using the standard FileReader API every browser provides, the same primitive the real editor is built on. It is never attached to a form, never given a URL, and there is no upload code on this page for it to be sent through even by mistake. The request counter next to it not moving after you pick a file is the actual, checkable proof — not a claim alongside it.
Does this page carry analytics or ads like the rest of the site?
No, deliberately, and it is the one other page besides the editor itself where that is true. Analytics elsewhere on this site is real but limited and disclosed — an anonymous page-view count, nothing about your files, which cannot exist because no document ever reaches a server anywhere on this site. But a page whose entire argument is "watch what actually gets sent" should not be sending its own traffic while making that argument, so this one carries none.