What PDFNexa receives, and how PDF files are handled in your browser.
This policy describes how PDFNexa handles site information today. The current PDF tools run locally in your browser: selecting a file for one of these operations does not upload its contents to PDFNexa. Contact messages and ordinary site technical data are handled separately.
Start with what the site actually does today.
PDFNexa is a WordPress site that publishes PDF guides, tool pages, legal information, accessibility guidance, and a contact form. The current PDF workspaces process selected documents in the visitor’s browser; PDFNexa does not receive the PDF for server-side processing.
That distinction matters. Reading a guide, sending a support message, and uploading a private PDF are very different privacy events. This policy keeps them separate.
Visitors can read the site without creating a PDFNexa account. Ordinary web requests still create technical connection data at the hosting and security level.
The contact form asks for a name, email address, topic, message, and optionally the page URL involved. It does not provide a PDF upload field.
The current PDF operations run in your browser. PDFNexa does not receive or store the selected PDF for server-side processing; check each tool’s file limits and output.
This policy will be updated when a specific advertising or analytics service is enabled and its data use is known.
A support request should not become a document dump.
The PDFNexa contact form is designed for reporting a page problem, requesting a correction, raising a privacy or advertising concern, or describing an accessibility barrier. It is deliberately not a file-upload channel.
Information you may provide
- Name
- Email address
- Selected topic
- Message text
- Page URL, when you choose to include it
This information is used to read, route, investigate, and respond to the message.
Information we ask you not to send
- PDF contents or private attachments
- Passwords or one-time codes
- Identification numbers
- Bank or payment details
- Medical records
- Confidential client or workplace material
If a technical problem needs a sample file later, use a document you created yourself with invented information unless a separate secure process is provided.
A web request carries information even when you do not fill in a form.
Web hosting, network, and security systems may receive technical information needed to deliver pages, diagnose errors, and protect the site from abuse. This is separate from the document content a future PDF processor may handle.
This may include IP address, request time, requested URL, referring page where supplied by the browser, browser type, device or operating-system information, and response status.
Hosting or security systems may record failed requests, suspicious traffic, rate-limit events, error details, or other information needed to keep the service available and investigate abuse.
Authorized site administrators may create technical records when managing WordPress, publishing content, responding to messages, or maintaining the site.
Not every browser connection comes from a cookie.
PDFNexa may use technically necessary browser storage or cookies where WordPress or a site feature requires them. Optional analytics or advertising cookies are not treated as active merely because a policy mentions them. See the separate Cookie Policy for the current cookie categories and controls.
Google Fonts
The current PDFNexa theme loads font resources from Google Fonts infrastructure, including fonts.googleapis.com and fonts.gstatic.com. Your browser may therefore make a direct request to Google when loading those resources, which can expose ordinary connection data such as IP address and browser request information to that provider.
That connection is different from sending a PDF or completing the contact form.
Necessary site functions
WordPress and security-related functions may use short-lived tokens, cookies, or similar mechanisms when needed to protect forms, maintain administrative sessions, or prevent abuse.
PDF tools operate locally in your browser.
The current tool workspaces accept a selected PDF and perform supported operations in the browser. Each tool page should state its file type and size limits, output format, and limitations for sensitive or signed documents.
Do not include a private PDF in the contact form. Keep the source document and check the downloaded output before sharing it.
We do not invent a data flow before the service exists.
If PDFNexa enables an analytics or advertising provider, this policy and the relevant consent controls will be updated to identify the provider, the purpose of processing, the categories of data involved, and the choices available to visitors where required.
Advertising placement is also governed by our separate Advertising Policy. Ads should not be presented as upload, download, navigation, warning, or document-action controls.
Running a website requires service providers, but that is not the same as selling your message.
Information may be handled by service providers that support the operation of the site, such as web hosting, network or security infrastructure, email delivery used to receive contact messages, and external resources such as the font provider described above.
Information may also be preserved or disclosed when reasonably necessary to comply with applicable law, respond to a valid legal process, investigate abuse, protect the service, or protect the rights and safety of users or others.
PDFNexa does not sell the contents of support messages. The current PDF tools do not upload document contents to PDFNexa for server-side processing.
Different records have different lifetimes.
We do not claim that every category of information is deleted on the same schedule. Retention depends on why the information exists, the systems involved, security needs, and any legal obligations.
Ask about information you actually provided to PDFNexa.
Depending on where you live and which law applies, you may have rights concerning personal information, such as requesting access, correction, deletion, restriction, or objection, or withdrawing consent where processing is based on consent. These rights are not identical in every jurisdiction and may be subject to exceptions.
If your request concerns a message you sent through the contact form, provide enough information for us to locate the correspondence without sending unnecessary identity documents.
Where optional consent controls are available, you can use them to change those preferences. Browser settings may also allow you to remove or block cookies.
We may need to verify that a requester is entitled to act on the information involved before fulfilling a privacy request. We will not ask for more information than reasonably necessary for that purpose.
Privacy starts before you click Send.
No website can promise absolute security. PDFNexa uses ordinary web and administrative safeguards appropriate to the service, but visitors should still avoid sending sensitive material through a general support form.
Highly sensitive, regulated, confidential, or consequential records should be handled through a system that has been approved for that information. A convenient web tool is not automatically the correct place for identity records, medical information, financial records, legal evidence, payroll, children’s information, or confidential client files.
PDFNexa is not designed as a children’s service.
The site is a general document utility and publishing resource. Do not use the contact form or any future processing feature to submit a child’s personal information unless you have the appropriate authority and the service is suitable for that information.
The policy should change when the product changes.
PDFNexa may revise this policy when site features, providers, processing methods, consent controls, advertising, analytics, or legal requirements change. The “Last updated” date at the top identifies the current version. A material change may also be highlighted on the relevant page when that context helps visitors understand what changed.
Start a privacy request through the contact page.
Choose “Privacy request” and describe what you need without attaching a private document or sending identification records unless a separate verification process is provided. The same contact route can be used to report a privacy statement that appears inaccurate or out of date.