Contact & Support
pdff.online is run by one person, and everything that arrives is read. If something here is wrong or does not work, that is genuinely useful to hear about.
Where to send what
| If your message is about | Send it to | Subject line |
|---|---|---|
| A tool that fails or gives a wrong result | accts.pak@gmail.com | PDFF bug report |
| Something inaccurate on the site | accts.pak@gmail.com | PDFF correction |
| Privacy, access, erasure or objection | accts.pak@gmail.com | Data request |
| A security vulnerability | accts.pak@gmail.com | SECURITY - see below |
| Advertising or sponsorship | Advertising page | PDFF advertising |
| Licensing, embedding or white-label | Licensing page | PDFF licensing |
| A review you believe is not genuine | Reviews page | PDFF review concern |
What makes a bug report useful
Four things, and it can be fixed much faster with them:
- Which tool. The page you were on.
- Which browser and version. Chrome, Firefox, Safari or Edge, and roughly its version.
- What you did and what happened instead. The actual behaviour is more useful than a description of the problem.
- The structure of the file, if a specific PDF fails. Whether it has AcroForm fields or is XFA, and whether it is a scan or has selectable text. Form fields from banks and tax authorities are usually XFA, and that single distinction explains the majority of reported form-filling failures.
Before you write
Most reported problems fall into one of the limitations already documented in Terms of Use, section 5:
- Redaction does not destroy the underlying text.
- Password protect and unlock were withdrawn and never worked.
- Form filling needs genuine AcroForm fields; XFA is unsupported.
- PDF-to-Word converts selectable text only and does not OCR.
If your issue is one of these, the answer is already there and you have not lost anything by checking.
Security disclosures
If you find a vulnerability, email accts.pak@gmail.com with "SECURITY" in the subject line. Please include a description, the affected URL, and steps to reproduce.
Please allow reasonable time for a fix before disclosing publicly. A working exploit should not be posted while a fix is still in progress. There is no bug bounty, and the Operator will not offer payment, but genuine reports are read directly and acknowledged.
Please do not access other users' documents, run automated scans against the infrastructure, or test in ways that degrade the Service for others. Authorised research on the Service itself, rather than its users' files, is welcome.
Response time
Bug reports are usually answered within a few working days. Data requests are acknowledged within seven days and actioned within one month, as set out in the privacy policy.
Round-the-clock support is not offered, and pretending otherwise would be another claim this site does not make.
Corrections
If the site states something that is not true, that is a defect and a priority. Corrections are made publicly visible rather than applied quietly, and the about page maintains a record of claims that were removed and why.
No analytics on this page
This page ships without a tracking script. Aggregate analytics are collected only on the tool pages, and only if you accept them in the cookie banner. Your documents are processed locally and are never transmitted. See the privacy policy.