Privacy

What happens to a file you open here?

Nothing leaves your device. Every tool in this suite runs as WebAssembly code inside the page you already loaded, so your file is read by your browser, worked on in your browser’s memory, and written back to your own disk. There is no upload step, no processing queue and no document storage: we operate none, so there is nothing for us to keep, lose or hand over.

You do not have to take that on trust. The how it works page carries a four-step procedure for watching your browser’s own network panel while a tool runs.

Accounts and the contact form are the only places where anything about you is stored, and both are described further down. Neither of them ever touches a document: an account holds no file, and the contact form has no upload.

What does the site measure?

Page views and loading speed, through Vercel Web Analytics and Vercel Speed Insights. Both are cookieless: they set nothing on your device, assign you no identifier, and cannot follow you to another site. They record which page was opened, roughly where from, on what kind of device, and how fast it rendered. Query strings are not reported at all, because the allowlist that would permit them is empty, so a filename or a setting you put in the address bar never reaches a measurement request.

Are there cookies, ad trackers or session recordings?

No. This site loads no Google Analytics, no session recorder, no advertising script and no third-party tag of any kind, which is also why you are not shown a consent banner: nothing here needs your consent to run. If that ever changes, the tag will load only after you agree to it, and this section will say so before it does.

What if I create an account?

Then we hold what an account needs and nothing else: your name, your email address, a hash of your password and the record of your open sessions. The password itself is never stored. Sign-in is handled by Better Auth against a schema of our own in a Postgres database we run, and you can also sign in with Google or with Microsoft, in which case that provider tells us your name, your email address and an account identifier, and learns that you signed in here. Verification and password-reset mail is sent through Resend. An account is only ever for pdfhq: there is no shared sign-in across our other products, and nothing is shared that could create one.

What happens to a message I send through the contact form?

It becomes an issue in a private repository on GitHub that only the people who build pdfhq can read. What travels is what you typed: the category, the message and, if you chose to give one, your email address, which we use only to reply. Nothing else is attached, and no file can be: the form takes text and has no upload. Leave the address empty and the message arrives with no way to identify you.

What is stored in my browser?

Two small things, both readable and removable by you. Your appearance choice is kept in local storage under the key “theme”, and a “NEXT_LOCALE” cookie remembers which of the three languages you last read, holding a two-letter code and nothing else. Neither is sent anywhere. Clearing site data in your browser removes both.

What does the offline cache keep?

The interface and the engine binaries, so a tool you have used once keeps working without a connection. The cache holds program code, never documents: no file you open and no result you produce is written to it. You can empty it from your browser’s site settings, and the app picks up a fresh copy on your next visit after we publish an update.

Where do the engines come from?

From this domain. Every WebAssembly binary and OCR language pack is served from pdfhq.app at a version-stamped address rather than from a third-party network, so opening a tool contacts no other company. Your browser checks each binary against its expected SHA-256 before it runs it.

Who serves the pages?

Vercel, from its Washington DC region. Like any web host it processes standard request data to deliver a page: your IP address, the address you asked for, and your browser’s user agent string, kept briefly for operations and abuse handling. That is the only point at which your IP address is seen, and it is seen for the page itself, never for a document.

What rights do I have over my data here?

The rights you have anywhere: to ask what is held about you, to have it corrected or erased, and to object to processing. Without an account the answer is short, because the suite then holds no identifier for you at all, and it never holds a document either way. With an account, the profile page lets you rename yourself, change your password and delete the account outright, which removes the record and every session with it.

How do I reach a person about this?

Through the contact form, or by email at the address on the imprint. Corrections to this page go to either: if something here is wrong or has fallen out of date, tell us and we will change it and move the date at the top.