PDFixer Privacy Policy

Last updated: september 2026

This policy describes which data PDFixer and the website pdfixer.fabreasy.com process, why, for how long, and which choices you have. It is written so that an administrator or data protection officer can place it next to a record of processing activities.

Controller: Yellow Smile ICT Services, trading as Fabreasy, Henry Dunantlaan 16, 2614 GH Delft, the Netherlands, Chamber of Commerce no. 24292836. Privacy contact: pdfixer@fabreasy.com.

1. Your documents stay on your computer

PDFixer edits, signs and protects PDF files locally. Documents, document names and document content are never sent to Fabreasy or to anyone else. The trial period is tracked locally, in the registry and in a file on the computer. Every outbound connection is listed below; there are no others.

2. Anonymous usage statistics

PDFixer periodically sends counters to pdfixer.fabreasy.com/telemetry.php to see which features are used and where the product can improve.

• What: a randomly generated installation ID (unrelated to your name, machine or license), the application version, the interface language, the distribution channel (download or Microsoft Store), which interface layout is active, screen resolution and scale, the license type (trial, paid or expired), the number of trial days used, the number of days since installation, and per-feature counters: launches, opens, saves, signatures, images, text, pages, letterhead, printing, watermark, form fields, symbols, stamps, and the use of the license and update prompts.
• What not: no name, e-mail address, user name, machine name, license key, file names or document content. The receiving server does not record an IP address with this data.
• Legal basis: legitimate interest in anonymous product statistics.
• Retention: at most 24 months as individual records; after that only as aggregated figures.
• Opt out: registry value Telemetry = 0 in HKLM\SOFTWARE\Fabreasy PDFixer (machine-wide, enforced) or HKCU\Software\Fabreasy PDFixer (per user). PDFixer then sends nothing, and the Microsoft Store rating prompt is not shown either.

3. License validation

A paid license is a named-user license: every Windows user who activates PDFixer with the key takes a seat. For this, PDFixer talks to the license server at pdfixer.fabreasy.com.

• On activation: the license key, the Windows user name (as the seat name), the origin in the form computername\username, and the application version. On a terminal server the domain name is used instead of the computer name.
• On the periodic check: the license key, the Windows user name and the application version. This check never adds a seat.
• On releasing a seat: the license key and the Windows user name.
• Stored on the server per seat: user name, origin, application version, first and last contact. Per license: key, e-mail address of the license holder, number of seats, expiry date, payment references and the e-mail language. The license holder sees these seats in the license portal and can release them.
• IP address: used only to limit the number of requests per address, and deleted after ten minutes. It is not linked to a license or seat.
• Legal basis: performance of the license agreement.
• Retention: a seat with no contact for 90 days is released automatically. 24 months after a license expires or is revoked, the e-mail address and user names are replaced by a hash and the remaining personal data is deleted.
• Privacy mode: registry value PrivacyMode = 1 replaces the computer name and the Windows user name with a hash. No personal data is then sent to the license server. With your own secret in PrivacySalt, not even Fabreasy can recover a name. The license holder then sees codes instead of names in the portal.

4. Purchase and invoicing

Licenses are purchased at pdfixer.fabreasy.com. Users who install PDFixer from the Microsoft Store also buy the license on our site; no payment goes through the Store.

• What: name, e-mail address, organisation, country, VAT number, the number of seats purchased, the invoice amount and the payment reference. The license key and the invoice are sent by e-mail from our own mail server. For an annual license you receive a reminder about 30 days before renewal.
• Payment providers: Mollie B.V. (the Netherlands) for buyers in the European Union; Dodo Payments (United States, as merchant of record) for buyers outside the EU. The payment provider receives the data needed for the payment; Fabreasy never sees your card or bank details.
• Legal basis: performance of the agreement and the statutory tax retention obligation.
• Retention: invoice data seven years (tax retention obligation). Other data as in section 3.

5. Update check

The download version of PDFixer asks pdfixer.fabreasy.com at startup which version is the latest and what the current price is. Only the application version is sent. The Microsoft Store version does not do this; updates come through the Store. Opt out: registry value AutoUpdate = 0.

6. Digital signing

When signing with a certificate, PDFixer uses a certificate from your Windows certificate store or from your eIDAS card or token. The certificate and the private key never leave your computer. The following does happen:

• The name and the issuer on the certificate are embedded in the signed PDF file, so the recipient can see who signed. That is the purpose of a signature.
• For the timestamp, PDFixer sends a SHA-256 hash of the document, together with a random number, to the timestamp service of Certum (Asseco Data Systems S.A., Poland). The service cannot derive the document from that hash and receives no name or document content.
• For long-term validation (PAdES-LT), PDFixer downloads revocation lists from the issuer of your certificate, at the addresses contained in the certificate itself.

Nothing is sent to Fabreasy when signing. Verifying a received signature happens entirely locally.

7. Website

The website runs on WordPress. As usual, the web server keeps technical logs with IP address, time and requested page; these are kept for at most five weeks. [CHECK: cookies. If the site uses functional cookies only, write: “The website sets functional cookies only and uses no advertising or tracking cookies.” Otherwise name the cookies.]

8. Hosting and processors

• Hetzner Online GmbH, Germany: hosting of the website, the license server, the telemetry, the database and the mail server, including backups. Data at rest stays within the European Economic Area. Backups are overwritten automatically within seven days.
• Mollie B.V., the Netherlands: payments within the EU.
• Dodo Payments, United States: payments outside the EU. Only buyers outside the EU come into contact with this.
• Certum (Asseco Data Systems S.A.), Poland: timestamps for digital signing.
• Microsoft: only when you install PDFixer from the Microsoft Store. Microsoft’s privacy statement applies; Fabreasy receives no personal data from Microsoft.

Fabreasy does not sell or share data with any party other than those listed above. There is no transfer outside the EEA, except the payment through Dodo Payments for buyers outside the EU.

9. Security

All traffic with pdfixer.fabreasy.com uses HTTPS. The license key and license status are stored on your computer encrypted with Windows DPAPI, bound to the Windows user. Every PDFixer executable is digitally signed and verifies that signature at startup. Access to the license server is limited to what administration requires. In the event of a personal data breach, Fabreasy informs the affected license holders without undue delay.

10. Your rights

You have the right to access, correct and delete your data, to restrict and object to processing, and to receive the data you provided yourself in a portable form. Send your request to pdfixer@fabreasy.com. You can lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

11. For administrators: all settings at a glance

Key: HKLM\SOFTWARE\Fabreasy PDFixer (machine-wide, takes precedence) or HKCU\Software\Fabreasy PDFixer. See also the FAQ for administrators.

Last updated: September 2026. Whenever what PDFixer sends changes, this policy is updated in the same release.