pdfmakeTOOLKIT
Legal

Cookies and tracking

This site sets no cookies and uses no analytics, advertising or tracking services. This page explains what that means in practice, what requests are still made to third parties, and how you can confirm it for yourself.

What is not here

No cookies are set by this domain, for any purpose, including ones that would ordinarily be considered strictly necessary. Nothing needs to be remembered between page loads because there are no accounts, no sessions and no preferences to store.

There is no analytics platform, no advertising or remarketing tag, no social media pixel, no session recording, and no fingerprinting. No profile of you is built, because nothing is collected to build one from.

This is why no consent banner is displayed. Consent is required for storage and tracking that is not strictly necessary; where neither takes place, there is no consent to obtain.

What does still leave your browser

Three requests are made to servers other than ours whenever a page loads.

The PDF libraries that power the tools are fetched from a public content delivery network. Typefaces are fetched from a font service. In both cases your browser makes a request, and the operator of that service can see your IP address and general request details, as they would for any resource loaded from anywhere on the web. Neither receives your document. The libraries run locally on your machine.

The server delivering these pages also records ordinary request information in its logs. That is described on the privacy page.

If you would prefer nothing third-party at all

The libraries and the fonts can be served from this domain instead, which removes those external requests entirely. Whether that has been done is a configuration choice, and this page will be updated to say so if it changes.

Browser extensions that block third-party requests will generally not break the tools, though blocking the content delivery network will prevent the PDF libraries from loading and the tools will report that they could not start.

How to verify this

Open your browser's developer tools, switch to the network tab, and reload any page. You will see requests for the page itself, its stylesheet, its script, the fonts and the libraries, and nothing else. Then check the storage or application tab: the cookie list for this domain will be empty.

This takes under a minute and is worth doing on any site that claims what this one claims.

Contact

If you have a question about what this site requests from third parties, or you believe something is being set that this page does not describe, please tell us and we will investigate.