Security and privacy are part of the workflow

Security for an online file tool is not a single badge or setting. It includes how uploads are stored, who can request a result, how long processing files remain available, how accounts are authenticated, and which optional third-party scripts may run. This page describes controls that are implemented by LoveMyFiles today. It does not claim that any internet service can eliminate every risk.

Uploaded processing files are stored outside the public web directory. A file is associated with a processing job rather than exposed as a predictable public asset. Job pages and downloads check the matching signed-in user or guest identity before returning private processing information. Knowing or guessing a filename is not intended to provide access to another person's job.

Guest ownership uses a browser identity token. The stored record uses a hash rather than keeping that token in readable form. Signed-in workflows use the authenticated account and ownership relationship. These controls reduce accidental cross-account access, but users should still avoid sharing job links, browser sessions, passwords, or downloaded files with people who should not receive them.

Processing jobs receive an expiry time based on the account type at upload. A scheduled cleanup command removes expired job directories and their completed records. Current maximum retention windows are:

• Guest files: within five minutes after upload.
• Free signed-in account files: within two hours after upload.

These windows describe the maximum scheduled availability, not guaranteed storage periods. A failed job may have partial output removed earlier, and users should download valid results promptly. LoveMyFiles is a processing service, not a permanent document backup. Keep an independent copy of every source and result that matters.

Account-only pages require authentication. Passwords are handled through the application's authentication system and reset workflow rather than being displayed in the profile. Where Google sign-in is configured, the external provider handles the Google authentication step and returns the account identity needed by the application. Administrative routes are separated from member routes and require administrative access.

Members can review their profile, credits and processing history. If you suspect unauthorised access, reset the password, end access to the account where possible, and contact us through the contact form with enough information to identify the account without emailing confidential document contents.

Necessary storage supports sessions, request protection, language routing, guest ownership, and the consent record. Optional analytics and advertising integrations are controlled through consent choices. Declining an optional category prevents its future activation through the consent mechanism. The Privacy Policy and Cookies page describe the categories and the role of third-party providers in more detail.

File validation checks expected extensions and formats for supported workflows, but no validation system can make an unsafe or untrusted document harmless. Do not upload files unless you have the right to process them. Do not use unlocking, editing, watermark, signature, or redaction tools to misrepresent a document, bypass another person's rights, or conceal unlawful activity.

Review every output. Conversion can change fonts, layout, formulas, reading order, transparency, metadata, or image quality. Redaction must be checked to confirm that sensitive content is removed from the actual output, not merely covered visually. Password protection is only one part of controlling access after a file has been downloaded and shared.

Report account-access, privacy or file-handling concerns through the [contact form](/en/contact#contact-form). Include the page URL, approximate time, browser, and a description of what happened. Do not attach confidential source files unless support specifically requests a safe method. Clear reports help the issue be reproduced and addressed without making promises before the facts are known.