Contact PDFNova for technical support, accessibility feedback, business questions, feature suggestions, or policy-related requests. A clear message helps the team understand the issue and respond efficiently. Before contacting support, note the tool name, browser, device type, file format, approximate file size, and the step where the problem occurred. Do not send passwords, identity documents, financial records, medical information, confidential client files, or any document you are not authorized to share. The website administrator’s current email address is displayed below so visitors can use their preferred email application.
How to Reach the Team
The primary contact method is email because it creates a clear written record and allows technical details to be reviewed carefully. Use the address shown on this page and write a specific subject line, such as “Merge PDF error in Firefox” or “Accessibility feedback for the tool directory.” General messages such as “the website is not working” can be difficult to diagnose. Include enough context for the team to identify the affected page, but remove confidential information before sending. PDFNova does not ask visitors to email account passwords, encryption keys, full payment details, or private source documents.
Information to Include in Support Requests
A useful support request includes the exact tool name, the page address, the browser name and version, the operating system, the device type, the source file format, and the approximate file size. Explain what you expected to happen and what actually happened. Copy any error message exactly instead of paraphrasing it. If the problem occurs only with one document, describe its general structure, such as scanned pages, forms, embedded fonts, or many high-resolution images. A small sample file containing no sensitive information can be helpful when the team specifically asks for one.
Reporting a Technical Bug
When reporting a bug, list the steps needed to reproduce it from a fresh page load. Mention whether the issue continues after clearing the browser cache, disabling extensions, and testing in a private browsing window. Screenshots can be useful when they show interface behavior or error text without exposing confidential data. Avoid sending an entire private document merely to demonstrate a visual issue. The team may request console information for advanced browser problems, but only provide it after reviewing the text for tokens, personal data, internal addresses, or other details that should not be shared publicly.
Conversion Quality Questions
Conversion quality depends on the source document and the selected output. Scanned pages, unusual fonts, complex tables, macros, layered graphics, and proprietary office elements can change during conversion. When contacting support about quality, identify the source and output formats and describe the affected element. For example, explain that a table moved to another page or a specific font was substituted. Keep the original file and compare it with the result. PDFNova can provide general troubleshooting, but it cannot guarantee exact reproduction or certify a converted document for legal, archival, medical, or financial use.
Feature Requests and Product Suggestions
Feature suggestions are welcome when they describe the underlying problem rather than only naming a desired button. Explain who would use the feature, what file types are involved, whether local browser processing is important, and what a successful result should contain. Requests are evaluated for usefulness, privacy, browser support, security, maintenance, and performance. A feature may not be added when it requires an unreliable external service, creates unreasonable risk, or would be misleading without specialist software. Even when a request cannot be implemented, it can help identify confusing instructions or missing workflow guidance.
Accessibility Feedback
Visitors can report accessibility barriers involving keyboard navigation, focus visibility, screen-reader labels, color contrast, motion, zoom, text spacing, or touch controls. Include the page, browser, device, assistive technology, and the action you were trying to complete. Describe the barrier in practical terms, such as an unlabeled button or a dialog that could not be closed with the keyboard. Accessibility reports are treated as product-quality feedback and can be more useful than a general statement that a page is inaccessible. Please avoid including health information or other sensitive personal details that are not needed to explain the problem.
Privacy and Data Questions
Questions about browser processing, optional server processing, cookies, technical logs, contact-message retention, or third-party services should reference the relevant policy section whenever possible. A visitor may ask what information is associated with a support message or how a deletion request can be submitted. The team may need reasonable information to locate a message, but should not request more data than necessary. Identity verification may be required before acting on certain privacy requests. Applicable rights and response requirements vary by location, so the website owner may provide instructions based on the laws that apply to the request.
Copyright and DMCA Notices
Copyright complaints should follow the DMCA Policy rather than being sent as a vague support message. A complete notice generally identifies the protected work, identifies the material claimed to infringe, provides accurate contact information, includes statements required by applicable law, and carries a physical or electronic signature. Knowingly submitting a false claim can have consequences. The website owner may request clarification when a notice is incomplete. Questions about files processed privately in a visitor’s browser are different from claims about material actually published or linked by the website, so the notice should clearly identify the public location at issue.
Partnership and Business Inquiries
Business inquiries should explain the organization, proposed relationship, target audience, expected benefit, and any technical or editorial requirements. PDFNova does not accept arrangements that require misleading claims, hidden downloads, deceptive buttons, unauthorized tracking, or promotion of unlawful services. Sponsorship, advertising, integration, or content proposals must remain consistent with the website’s privacy and usability standards. Sending an inquiry does not create a partnership, confidentiality obligation, or commitment. Do not include trade secrets or confidential proposals until both parties have agreed on an appropriate process for reviewing protected information.
Security Vulnerability Reports
Potential security issues should be reported privately and responsibly. Include the affected page or component, a clear description of the behavior, the conditions needed to reproduce it, and the potential impact. Do not access data that does not belong to you, disrupt the service, upload malware, perform denial-of-service testing, or publish exploit details before the owner has had a reasonable opportunity to investigate. A report does not guarantee payment or participation in a reward program. The goal is to help correct genuine weaknesses while respecting user privacy, service availability, and applicable law.
Response Expectations
Response times depend on message volume, complexity, staff availability, and the information provided. Technical questions may require reproduction and testing before a useful answer can be given. Repeatedly sending the same message can slow review and may trigger spam controls. A response is not guaranteed for advertising solicitations, abusive messages, automated outreach, or requests that fall outside the website’s scope. When an issue affects many users or presents a serious security concern, it may be prioritized. Visitors should keep copies of important files and should not wait for support before preserving data or meeting an external deadline.
Messages We Cannot Process
The contact channel cannot provide legal representation, financial advice, medical guidance, emergency assistance, password recovery for third-party services, or certification that a document is valid. The team cannot unlock a file without the correct password, recover deleted files from a visitor’s device, or guarantee that a conversion will satisfy an institution’s requirements. Messages requesting unlawful access, copyright infringement, malware distribution, identity fraud, harassment, or evasion of security controls may be ignored or reported when appropriate. Use qualified professionals and official emergency channels for matters outside the website’s document-tool purpose.
Protecting Sensitive Information
Before sending a message, remove names, account numbers, signatures, addresses, case numbers, medical details, confidential business information, and embedded metadata unless they are genuinely required. Describe a document rather than attaching it whenever possible. If a sample is requested, create a redacted copy or a synthetic example that reproduces the technical issue. Email is not automatically a secure channel, and forwarding can create additional copies. The safest support request contains the minimum information necessary to understand the problem while keeping the original sensitive document under the user’s control.
Browser and Device Troubleshooting
Many tool problems can be resolved before contacting support. Refresh the page, update the browser, allow JavaScript, verify that the file is within the displayed limit, and test without privacy or script-blocking extensions. On mobile devices, close unused applications to free memory. For large or complex documents, try a smaller copy on a desktop computer. If an optional server feature reports that LibreOffice, QPDF, or Ghostscript is unavailable, the hosting provider must install and configure that program. Support cannot enable software that the current hosting plan does not permit.
Before You Send Your Message
Review the message for accuracy, remove unnecessary personal data, confirm the page address, and check that any screenshot is properly redacted. Use respectful language and one clear subject. Explain the desired outcome and identify any troubleshooting already completed. Keep your original file and any generated result because support may ask you to compare them. By contacting PDFNova, you acknowledge that the message will be processed for the purpose of reviewing and responding to the inquiry, subject to the Privacy Policy and the technical operation of the website’s email and hosting providers.