Who operates this service
LoveMyFiles is operated by Suraj Singh. This policy explains how information is handled when you browse, create an account, use file tools or contact us. Use the contact form linked below for privacy questions or requests.
Browser processing and server processing
Some image and collage operations process your files within your browser. Server tools, including PDF workflows and certain image conversions, receive files for processing. Read the processing notice on the tool you use; this policy does not mean every file stays on your device.
Browser processing can use memory or browser storage. File handoff between tools may temporarily store selected files on your device. Clearing site data can remove local state, and browser-only processing does not prevent other software on your device from accessing a file.
Files and processing records
Server-processed files are held outside the public web directory. Job pages and downloads require the matching account or guest identity. Processing records can include filenames, file types, size, checksum, tool options, status, timestamps and output information.
File content is used to perform the requested operation. Avoid uploading material you do not have permission to process. Keep your own originals and review the downloaded result.
Accounts and sign-in
Account information includes your name, email, authentication information, credit balance and processing history. Guests receive an identifier used for job ownership and usage limits. Where Google sign-in is available, authentication also involves Google and the account information it supplies to complete sign-in.
Contact requests
The contact form collects the fields you submit, including name, email, company, optional team size, message and the consent choice. Accepted enquiries are stored for administrative follow-up and may be sent through the configured email service.
Spam checks, rate limits and security records help protect the form. Do not put passwords, payment credentials or unnecessary private document contents into a message.
Operational and security information
Requests can expose IP addresses, browser or user-agent information, requested URLs and timestamps to hosting and security systems. The application also uses security-relevant identifiers and records to manage guest access, prevent abuse, apply limits and investigate failures.
Analytics, advertising and affiliate links
Configured analytics, including Google Analytics, can measure visits and interactions after the applicable consent choice. Advertising integrations may allow Google or other providers to place or read cookies, use web beacons and receive information such as an IP address, browser information and ad interactions.
Where enabled, Google advertising may use information from visits to this and other sites to provide advertisements, subject to consent and provider settings. Banner links can be affiliate links: LoveMyFiles may receive a commission if you make a qualifying purchase. Following an external advertiser link takes you to that provider's service and privacy rules.
Service providers and optional document providers
Hosting, security, email, authentication and enabled analytics or advertising providers receive information needed for their functions. Features configured to use an external document or AI provider may send extracted text, your question or translation content to that provider. Check the feature notice before submitting confidential material.
A provider's location and retention practices can differ from LoveMyFiles. This page does not promise that all service providers process data in one country or that an external provider deletes information at the same time as a local job.
Retention, expiry and deletion
PDF job access expires after five minutes for guests or two hours for free accounts. Scheduled cleanup removes expired processing files. These are job-availability windows; they do not mean every account, support message, security log or backup is deleted within the same period.
Some server image workflows remove temporary files when their request completes. Failed processing and uploads can follow different cleanup paths. Download results promptly; LoveMyFiles is not permanent file storage.
Account, support and operational records are retained to operate the service, handle enquiries, maintain security and meet applicable obligations. Backup copies, where present, are separate from live data and may not disappear immediately after a live record is removed.
Your choices and privacy requests
Use Cookie Settings in the footer to manage optional integrations. You can ask about access, correction or deletion of information associated with you through the contact form. Identify the account or enquiry involved, without including your password.
We may need to verify ownership before disclosing or changing information. Requests are assessed under applicable law and operational requirements; some records may need to be retained for security or legal obligations.
Children and sensitive information
Do not submit a child's personal information or sensitive information unless you have the necessary authority and the relevant tool is appropriate for that material. If information about a child has been submitted without appropriate authority, contact us so the request can be investigated.
Policy changes
We update this policy when processing practices or features change. Check the date shown on this page. A website policy does not replace the privacy obligations that may apply to your own use of other people's documents.
Short links and click analytics
Short links are saved under the creator account. We store the destination, alias, title, campaign settings, expiry and activity status; destination URLs and saved campaign settings are encrypted in the application database. A guest creation draft expires after 15 minutes and is checked again after sign-in.
Following a short link does not require an account or set analytics cookies. The analytics database records time, country when supplied by a trusted Cloudflare connection, approximate device, browser and operating system, language, referrer domain, campaign parameters and suspected bot or QR-tagged traffic. Referrer paths and query strings, raw IP addresses and full user-agent strings are not saved in this analytics database. Infrastructure access logs are separate.
Approximate visitor counts use a secret, per-link hash derived from the request address and browser information, rotated every 30 days. They are not verified people counts. QR-tagged clicks are not proof that a QR code was scanned. Region and city are not collected by this feature.
Detailed events are retained for up to 90 days and daily aggregates for up to 365 days, with scheduled cleanup. Lifetime counters can remain while the link exists. Deleting a link removes its analytics and destination data; the reserved alias and brand remain unavailable for reuse. Only the owner and authorized administrators can manage links; per-link analytics requires owner authentication.