Privacy Policy

1. Our approach

SafePDFHub is designed around a simple principle: your files are yours. Where a feature is implemented for local browser processing, the PDF or other document is processed on your device rather than uploaded to a SafePDFHub file-processing server.

Because the exact data flow can differ by feature and may change as the product evolves, we aim to describe those changes clearly rather than make a blanket promise that every future feature will always be local.

2. Files and documents

For browser-local tools, your selected files are read by the web application in your browser. We do not intentionally receive those document contents through the website's application servers.

Do not assume a feature is local if the interface explicitly says that a third-party service or remote processing is required. We will identify such requirements where applicable.

Word to PDF conversion

Word to PDF reads DOCX documents and generates downloadable PDFs locally in your browser. Documents are not sent to a conversion service, and conversion does not require the browser print dialog. Required application code and conversion fonts load from this website.

3. Information you provide

If you contact us, you may provide information such as your name, email address, subject, and message. The Contact page sends that information through a first-party SafePDFHub server endpoint so we can receive and respond to your request. We do not store contact messages in the PDF processing system or use them as document-processing data.

If you later use a payment service or another hosted service, that provider may collect information necessary to provide its service. Its own privacy policy will apply to information it processes.

4. Automatically collected information

Web hosting, security, performance, analytics, advertising, or other infrastructure providers may process technical information such as IP address, browser type, device information, request timestamps, or diagnostic data if those services are enabled.

When configured on our production website and you accept usage analytics, Google Analytics measures visits, approximate country and device information, referring website, and tool activity. Tool events contain fixed tool labels, broad file-size bands, processing duration, and generic success, cancellation, or failure status. We do not send document contents, filenames, passwords, signatures, recognized text, or raw processing errors to analytics.

If you separately accept public-page recordings, Microsoft Clarity provides interaction recordings and heatmaps on selected public pages. Page content is masked, and Clarity is not loaded in PDF tools, Studio, result pages, or the contact form. When leaving a recorded public page, the website performs a full page navigation to unload the recorder before opening another page. We do not use Clarity to record your documents.

Our hosting provider, Netlify, may separately process technical request logs and provide server-side traffic statistics. Browser analytics choices do not control hosting logs needed to deliver and secure the website. Google Search Console provides aggregate Google Search performance information.

5. Cookies and similar technologies

Optional Google Analytics and Microsoft Clarity scripts load only after the corresponding consent choice. Rejecting optional tracking does not restrict PDF tools. We store your choices in local storage for up to 180 days, then ask again. Use the Privacy choices control to change or withdraw consent. If a recorder is running on a public page, withdrawing recording consent reloads that public page to unload it completely. An active PDF workspace is not reloaded.

Google Analytics and Microsoft Clarity may use cookies when you opt in. Advertising consent is kept denied. We remove the first-party analytics cookies we can access when the relevant choice is withdrawn. Consent preferences are necessary to remember your decision; they are not document data. See Google’s privacy policy and Microsoft’s privacy statement for provider information.

6. Third-party services

Some product infrastructure may rely on third-party libraries or services. A browser library used to process a document locally is different from a service that receives the document on a remote server. For the Contact form, SafePDFHub currently uses Resend as its transactional email delivery provider to deliver messages to our support mailbox. Resend processes the contact information needed to deliver the email; the PDF processing system does not receive or store the submitted message. If the provider changes, this section will be updated accordingly.

7. Security

Local processing can reduce the need to transmit document contents, but no website or device can be guaranteed completely secure. Keep your browser, operating system, and security software up to date and use only trusted devices for sensitive documents.

8. Children's privacy

SafePDFHub is not intentionally directed at children. If you believe a child has provided personal information to us, contact us so the situation can be reviewed.

9. Changes to this policy

We may update this policy when SafePDFHub's features, infrastructure, or legal requirements change. The date at the top of this page indicates when the current version was published.

10. Contact

For privacy questions, please use the Contact page.