GDPR at GoodPDF

For the documents you work on, nobody at GoodPDF is a controller or a processor, because we never receive them. They are opened, edited and saved by software running on your own machine.

For the data around your licence — your email address, your key, and which devices it is activated on — GoodPDF Limited is the controller. We decided to collect it and we decide what happens to it.

There is one narrow case where we act as a processor: a problem report you send from inside the application includes the document you had open. For that report, and only that report, we are handling content on your behalf.

• Email address — to send you your licence key, receipts and recovery links. Legal basis: performance of a contract.
• Licence key, installation identifier, platform and device name — to enforce the three-device limit and to let you move a licence to a new machine. Legal basis: performance of a contract.
• Payment records held by our payment processor — to take payment and meet tax obligations. Legal basis: contract and legal obligation.
• Crash reports — to find and fix faults. Legal basis: legitimate interest in a working product.
• Problem reports you choose to send, which include the open document and a screenshot. Legal basis: your explicit action in sending them.
• Aggregate website analytics with no cookies and no cross-site identifiers. Legal basis: legitimate interest in knowing which pages are read.

• No account and no password — the software is unlocked with a key, so there is no profile to build on.
• No tracking cookies on goodpdf.io, and therefore no consent banner to click past.
• No advertising identifiers, no data sold or shared with data brokers, no profiling and no automated decision-making that produces legal effects.
• No collection of document contents, filenames or file paths outside a report you sent us on purpose.

If the GDPR or the UK GDPR applies to you, you have the right to access the personal data we hold about you, to have it corrected, to have it erased, to restrict or object to our processing, and to receive it in a portable form. You also have the right to withdraw consent where processing relies on it.

Because we hold so little, most of these are quick to answer. Note that erasing a licence record ends the licence itself, so we will confirm that is what you want before doing it.

Write to us from the contact page using the address you bought the licence with, or tell us which address it was. We do not charge for requests and we aim to answer well inside the statutory month.

If you are asking us to delete a problem report you sent, give us the approximate date and the file name if you remember it, so we can find the right one.

Our sub-processors operate globally and personal data may be processed outside the EEA, including in the United States. We rely on the European Commission's Standard Contractual Clauses, with the UK Addendum where it applies.

We do not currently offer EU-only data residency. The named sub-processors are listed in the Data Processing Agreement.

If you think we have handled your personal data badly, tell us first — it is usually the fastest way to get it fixed. You also have the right to complain to your local supervisory authority, and doing so does not require you to contact us first.

We do not have an appointed EU representative or a designated Data Protection Officer. Given the volume and nature of the personal data involved — no special categories, no profiling, no large-scale monitoring — we do not believe either is required, but a vendor review will ask, so it is stated here rather than left to be discovered.

Problem reports are the one place where genuinely sensitive content can reach us, and they only get there because someone pressed send. That is a design decision, not an accident: a reproducible bug report is worth more than a vague one. It is also why the report screen says what it attaches.