What happens to a file you drop in
It is read by your browser straight from your disk, examined in memory, and gone when you clear the result or close the tab. It is never transmitted anywhere. There is no server, no database, no storage bucket and no upload endpoint, so there is no mechanism by which a file could be sent even by mistake.
That distinction is practical rather than decorative. It means you can check artwork you are contractually not allowed to send to a third party, which rules out every checker that works by upload.
How to verify that in thirty seconds
Do not take it on trust. Open your browser developer tools, select the network panel, and drop a file in. You will see no requests at all, because the page makes none: no analytics, no fonts from a font service, no scripts from a content delivery network, nothing.
The claim is also enforced mechanically rather than by good intentions. The build runs an automated test that inspects the finished page for a reference to any external host and fails if it finds one, so this cannot quietly stop being true after a careless change later.
What is not collected
- No cookies. None are set, of any kind, which is why there is no cookie banner to dismiss.
- No analytics. No Google Analytics, no Plausible, no tracking pixel, no fingerprinting, no session recording.
- No browser storage. Nothing is written to local storage or IndexedDB, so nothing at all persists between visits.
- No account, email address or payment details, because there is nothing here to sign up for.
What the web host can see
To be complete rather than merely reassuring: the pages, styles and fonts themselves are served by GitHub Pages, and like any web server it receives ordinary request information such as an IP address, the page asked for and a browser user agent. That is the same information every website you visit receives, and it is unavoidable for anything served over the internet.
It applies to the page, never to the file you check, which is not part of any request. Those logs are not exposed to me and I do not read them. GitHub's own handling of that data is set out in the GitHub privacy statement.
Third parties
There are none. The one typeface is served from this domain rather than from a font service, and the PDF reading is done by pdf.js, which is bundled into the page rather than fetched from anywhere. Nothing on this site talks to another company on your behalf.
If this ever changes
It will change on this page first, and the change will be visible in the site's history rather than announced quietly. There is no roadmap on which files start being uploaded, because the entire point of the tool is that they are not.
Contact
Questions about any of this, or about anything else, to contact@vecpath.com.