Get in touch with PDFWhirl
PDFWhirl is a small team that reads every incoming message. We have deliberately kept the list of contact channels short — support, privacy, security, press, partnerships, and legal — so you can pick the right one without guessing. This page explains when each channel is appropriate, how quickly you can expect a reply, and what to include in your message so we can help you on the first round.
Because PDFWhirl's free tier does not require an account, email is the primary way to reach us. There is no ticket portal, no chatbot, and no phone queue. Every message goes to a human — usually the person on the team best suited to answer, based on the mailbox you write to.
General support
Users with a question about a tool, a processing issue, a feature suggestion, or anything that does not fit another channel.
- The name of the tool you were using (for example, Compress PDF)
- What you expected to happen and what happened instead
- Browser name and version, operating system, and device type
- Error ID if one was shown, or a screenshot of the error
- Approximate size and page count of the file you were processing (do not attach the file itself)
Privacy questions
Anyone exercising a data-protection right (access, rectification, erasure, portability, objection, withdrawal of consent) or asking a question about how files are handled.
- A brief description of your request
- Which jurisdiction applies to you (EU, UK, California, Brazil, or other)
- Enough context for us to identify any data we hold, if the request relates to specific processing
- A preferred reply channel if different from the email address you are writing from
Security reports
Security researchers and users who have noticed something that looks unsafe — vulnerabilities, suspected misuse, unexpected behaviour that could indicate a bug with security impact.
- A concise description of the issue
- Steps to reproduce, or a proof-of-concept that does not cause harm
- The URL or endpoint where the issue manifests
- An indication of how we should credit you if the fix ships publicly
Press and media
Journalists, analysts, podcasters, and other members of the media looking for quotes, background, or company facts. Subject line should begin with “Press:”.
- Your publication or outlet name
- A short description of the piece you are working on
- Your deadline
- The specific question or quote you are looking for
Partnerships
Companies interested in integrations, distribution arrangements, co-marketing, or bulk licensing. Subject line should begin with “Partnership:”.
- A short description of your company
- The kind of partnership you are proposing
- Any relevant volume or integration details
- A decision-making timeline if you have one
Legal and intellectual property
Formal legal notices, intellectual-property complaints, subpoenas, and similar correspondence. Subject line should begin with “Legal:”.
- The legal basis for your request
- Contact details of the rights holder or representative
- Enough detail for us to identify the alleged material
- A good-faith statement and, where required, a signature
Before you email: things you might find faster elsewhere
Many of the most common questions we hear already have dedicated pages on the site. If you are in a hurry it is often faster to check those first:
- FAQ — a long list of specific questions about tools, file limits, privacy, and troubleshooting, grouped by topic.
- Guides & Help Center — longer-form articles on OCR, compression, merge strategies, and online-tool safety.
- Security page — the full details on how your files are protected, including encryption, retention, isolation, and responsible disclosure.
- Privacy Policy and Cookie Policy — the definitive documents on how data is handled and which cookies we set.
- Pricing — the current free tier, and what Pro will eventually cover.
Message templates you can copy
If you would rather start from a skeleton, these templates are a good starting point. Delete whatever does not apply; we will fill the rest in by asking.
Support: tool issue
Subject: Issue using [tool name]
Hi PDFWhirl,
I was trying to [describe the action, e.g. "merge four PDFs"].
Expected: [what you expected to happen]
Actual: [what happened instead, including any error message or error ID]
Environment:
- Browser: [e.g. Chrome 128]
- Operating system: [e.g. macOS 14.4]
- Device: [e.g. MacBook Pro / iPhone 15 / Pixel 8]
- File type and size: [e.g. one 40 MB scanned PDF; do not attach]
Thanks,
[Your name]Privacy: data request
Subject: Privacy request — [access / deletion / correction / portability]
Hi PDFWhirl,
I am writing to exercise my rights under [GDPR / LGPD / CCPA / other].
Specifically, I would like you to [describe the request].
For verification, I am writing from the email address I normally use with
your service. If you need any additional identifying detail, please let me
know and I will follow up securely.
Thanks,
[Your name]Security: vulnerability report
Subject: Security report — [brief description]
Hi PDFWhirl,
I believe I have found an issue on pdfwhirl.com.
Summary: [one-line description]
Endpoint / URL: [where the issue manifests]
Steps to reproduce:
1. [step]
2. [step]
3. [step]
Impact: [what an attacker could do with this]
Happy to coordinate on timing. Please credit me as [name / handle] when the
fix ships, if appropriate.
Thanks,
[Your name]Response times, holidays, and out-of-hours
The response times listed above are our targets under normal circumstances. Around major public holidays and during staffing transitions, turnarounds may be slightly longer; in that case we will do our best to acknowledge your message quickly even if the full reply takes a little longer. Genuine emergencies — an active security incident, for example — are triaged outside business hours via the security mailbox.
Languages
We reply in English by default. If you are more comfortable writing in another language, feel free to do so — we will understand most major European and Asian languages and reply in English with a translated reference where helpful. A fully multilingual support experience is on the roadmap.
What not to send us
Please do not email us your uploaded files. We do not need them to help you, and the less personal data you send the better. If we do need a sample file to reproduce a specific bug, we will ask for the smallest possible example and delete it immediately after the investigation. Do not send passwords, bank details, or identification documents by plain email.
Company address and legal notice
For formal legal notices that require a postal address, please write first to support@pdfwhirl.com with "Legal" in the subject line. We will respond with the correct address based on the nature of the notice.
Still stuck?
If you are not sure which channel fits, write to support@pdfwhirl.com. We will route the message internally. One email is always enough.