Table of Content7 Sections
Notice updated: . This notice describes ILovePDF.ltd’s toolkit and the support information published with it. The operator’s contact and review details, when published, appear on About. Hosting, mailbox, backup and any additional website services must be considered separately from the toolkit’s temporary document processing.
What Happens to Documents Processed in Your Browser?
Tools labeled “On your device” read selected files in the browser. Their conversion code does not upload those documents to a processing server. Modern DOCX, XLSX and PPTX conversion follows this route by default. The browser still requests the website’s pages, scripts, fonts and supporting assets, so visiting the page generates ordinary website requests.
The workspace holds active files and results while it is open. Resetting or closing it ends that working session; it does not delete files you have already downloaded or erase copies kept by your device, browser, backup software or another application. The toolkit does not provide a personal cloud document archive.
What Happens When You Choose Server Processing?
Optional Native Office export accepts DOCX, XLSX and PPTX files. Selecting a file alone does not upload it; starting native conversion does. The upload is held in private storage outside the public website and checked before an isolated processor opens it. Older Office formats must first be saved as DOCX, XLSX or PPTX in an office application.
Native processing requires an available malware scanner with current signatures, an isolated document processor and a working independent cleanup service. Flagged files, incomplete security scans and unsupported documents are rejected. Both the input and the generated result are scanned. Scanning reduces risk but cannot guarantee that every malicious file will be detected. Browser-only documents do not go through this server scanner.
The five-minute deadline starts when the application receives the upload request and includes scanning and conversion time. Successful jobs remove their input and intermediate files; handled failures remove the job files. Remaining results are scheduled for deletion at the original deadline, and download requests are refused at that deadline. The worker and an independent host cleaner enforce this lifecycle; new native jobs are refused when the required cleanup checks fail. Server outages or filesystem errors can delay physical removal. These rules cover the toolkit’s working storage, not separately managed hosting buffers, backups or logs.
A result link uses a long random token, but anyone possessing an unexpired link can download its file. Avoid sharing that address if the document is private. A saved download remains under your control after the server link expires.
How are Document Passwords Handled?
The browser password tools use a temporary processing worker, which is terminated when the job succeeds, fails or is canceled. The password input is cleared after those outcomes, when you use Clear files and when you replace the selected file. The processing code does not send the password to a conversion service. These measures do not promise secure erasure of every copy a browser or device may retain. Keep passwords out of support messages.
What Does the Contact Form Collect?
The form collects the name, reply email address and message you enter. These details are used to read your request and reply to it. The form passes them to the website’s configured mail service through WordPress mail, including your email as the reply address. A successful form notice means the mail service accepted the message for delivery; it does not confirm that a person has read it.
The theme does not create a permanent database copy of the message body. Copies can still exist in the receiving mailbox, sent replies, mail-service records, hosting logs or backups. Their retention is separate from the five-minute document deadline. The contact form does not accept file attachments.
Support email: [email protected]
Support availability: No fixed response time is currently published.
Support messages are retained in the support mailbox under its retention and backup settings. A fixed mailbox deletion period has not been published. The document-result expiry period does not apply to support emails.
You can request information about, or deletion of, a support conversation through Contact. Include the email address used and an approximate message date so the conversation can be located.
Why Does the Website Use Temporary Request Counts?
To limit repeated submissions, the contact form stores a count against a keyed hash derived from the connection’s IP address. That count is configured to expire after 10 minutes. Optional server conversion uses a separate hashed request count with a five-minute expiry. These entries contain the counter, not the contact message or document, and are separate from any ordinary access logs kept by the host.
What About Cookies, Logs and Other Website Services?
Hosting infrastructure can record IP addresses, request times and requested URLs. WordPress can use cookies for signed-in sessions. The toolkit does not include a third-party document-processing API or analytics integration. Other plugins, advertising, security tools or hosting services can have their own data handling; this description covers the toolkit’s implemented behavior and is not a statement that every website request is anonymous.
How Can You Ask About Your Data?
Use Contact to ask about a support message or request deletion of correspondence. Identify the email address and approximate date of the earlier exchange rather than resending private contents. The website operator’s published details are available on About. Do not include document passwords or confidential files when asking a privacy question.