iloveutil

Privacy Policy

Last Updated: January 8, 2026

Introduction

Welcome to iloveutil ("we," "our," or "us"). If you have ever hesitated before uploading a sensitive document to a random website, or wondered what happens to your files after you click that process button, this Privacy Policy is for you. We are going to explain exactly what data we collect, what we do with it, and more importantly, what we do not do with it.

Here is the most important thing to understand about iloveutil: when you use our tools to compress an image, merge a PDF, format JSON code, or do any other task, that processing happens entirely in your web browser using JavaScript. Your files do not get uploaded to our servers. They do not sit in some cloud storage bucket. They do not pass through our infrastructure at all. Your browser reads the file from your hard drive, processes it locally, and saves the result back to your device. We literally cannot see your files because they never reach us. There is no upload step, no temporary storage, no file retention. This is not marketing language—it is how the code actually works.

So what data do we collect? We use Google Analytics to understand how people use the site (which tools are popular, how long pages take to load, that sort of thing) and Google AdSense to display ads that keep everything free. Those services use cookies and collect some information about your visit. But they do not see the content of the files you process. If you compress a photo of your tax documents or merge PDFs containing client contracts, neither we nor Google has any idea what is in those files. The analytics track that someone used the PDF merger, not what PDFs they merged.

This Privacy Policy will walk through exactly what information gets collected (analytics data, advertising cookies), what third-party services we use (Google Analytics 4, Google AdSense), what rights you have (opt-out options, cookie controls), and how browser-based processing protects your actual work data. If you have questions after reading this, there is a contact form on the site. We are a small team, not a faceless corporation, and we actually read messages.

What Makes Our Privacy Model Different

Most online tools work like this: you upload a file to their server, their server processes it, then you download the result. This means your file passes through their infrastructure, which requires you to trust them not to keep copies, not to get hacked, not to use your data for training AI models, and not to scan your content for whatever purposes they might have. That trust can be uncomfortable when the file contains anything sensitive.

iloveutil works differently. When you select a file, your web browser reads it directly from your hard drive into its own memory. All the processing—whether that is compressing an image, merging PDFs, formatting JSON, or anything else—happens right there in your browser using JavaScript code. When processing finishes, your browser creates the output file and downloads it back to your device. At no point does the file travel over the network to our servers.

You can verify this yourself if you are technically inclined. Open your browser's developer tools, go to the Network tab, and watch what happens when you use a tool. You will see the page load initially (HTML, CSS, JavaScript files), but when you process a file, there is no upload request. The network is silent except for maybe loading an ad. Everything happens locally. Some tools would even continue working if you disconnected from the internet after the page loaded, though we do not officially support offline mode.

This architecture has real privacy implications. We cannot accidentally leak your files in a data breach because we never have them. We cannot comply with a subpoena demanding your documents because they never reach us. We cannot train machine learning models on your data because we never see it. We cannot even track what types of files you process—our analytics know someone used the PDF compressor, but not what PDF they compressed or what was in it. Your tax returns, client contracts, personal photos, proprietary code, medical records, financial statements—whatever you are working with stays entirely on your device.

Information We Collect

1. Analytics Data (Google Analytics 4)

We use Google Analytics 4 (GA4) to understand how visitors use our website and improve our services. GA4 collects:

  • Pages visited and time spent on each page
  • Browser type, device type, and operating system
  • Geographic location (country/city level only)
  • Referral source (how you found our website)
  • User interactions and engagement metrics

This data is collected using cookies and is anonymized. No personally identifiable information (PII) is collected through analytics. You can opt out of Google Analytics by using the Google Analytics Opt-out Browser Add-on.

2. Advertising Data (Google AdSense)

We use Google AdSense to display advertisements on our website. Google AdSense may collect:

  • Cookie data for ad personalization and frequency capping
  • Device and browser information
  • IP address (for geographic targeting)
  • Ad interaction data (clicks, impressions)

Google's advertising cookies are used to serve ads based on your prior visits to our website and other websites. You can opt out of personalized advertising by visiting Google Ads Settings or by visiting www.aboutads.info.

3. User-Provided Data (Your Files and Documents)

This is the most important section for most people. When you use our tools—whether that is compressing an image, merging PDFs, decoding a JWT token, calculating EMI payments, formatting JSON, or any other task—all processing happens entirely in your browser using JavaScript. Let us be extremely clear about what this means:

  • We do not upload your files to any server. The file stays on your hard drive and gets read into your browser's memory.
  • We do not store your data in any database. There is no server-side storage, no temporary files, no logs containing your content.
  • We do not transmit your content over the internet. Your files do not travel through our infrastructure or anyone else's.
  • We do not access, view, or analyze your documents, images, or text. We physically cannot see what you are working on.
  • We do not use your files for training AI models. This is becoming a common concern, and the answer is simple: we never have access to your files in the first place.
  • We do not scan your content for keywords or metadata. Your file contents are invisible to us.

What does this mean practically? If you compress a photo of your passport for a visa application, we do not see that photo. If you merge PDFs containing financial statements for a loan application, we do not see those statements. If you use the text tools to clean up copied content from a confidential report, we do not see that report. If you decode a JWT token from your company's internal API, we do not see that token. The processing happens locally on your device, and the result downloads directly back to your hard drive.

The only data we collect about tool usage is analytics metadata: someone used the image compressor at a certain time, from a certain country, using a certain browser. But what image they compressed? No idea. What was in it? No idea. How large was it? No idea. That information never leaves your device.

How We Use Information

We use the information collected for the following purposes:

  • Analytics: To understand user behavior, improve our tools, and optimize website performance
  • Advertising: To display relevant ads and generate revenue to support free tool availability
  • Service Improvement: To identify which tools are most popular and where to focus development efforts
  • Technical Maintenance: To detect and fix technical issues, bugs, or errors

We do not sell, rent, or share your personal information with third parties except for the third-party services mentioned (Google Analytics and Google AdSense) which have their own privacy policies.

Cookies and Tracking Technologies

We use cookies and similar tracking technologies for:

  • Analytics Cookies: Google Analytics cookies to track website usage
  • Advertising Cookies: Google AdSense cookies for ad delivery and personalization
  • Essential Cookies: Cookies required for basic website functionality

You can control cookies through your browser settings. Note that blocking cookies may affect your experience on our website and limit ad personalization.

Third-Party Services

We use the following third-party services, each with their own privacy policies:

Google Analytics 4

Analytics and website usage tracking

View Google Privacy Policy →

Google AdSense

Advertising and monetization platform

View Google Ads Policy →

Data Security

We take data security seriously. Since all tool processing happens client-side in your browser, your sensitive data never reaches our servers. We implement security best practices including:

  • HTTPS encryption for all website traffic
  • Regular security updates and monitoring
  • Secure coding practices to prevent vulnerabilities
  • No storage of user-generated content on servers

Children's Privacy

Our services are not directed to children under 13 years of age. We do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has provided us with personal information, please contact us.

International Users

Our website is accessible globally. If you are accessing our services from outside your region, please be aware that your information may be processed in countries with different privacy standards. By using our services, you consent to the transfer and processing of your information as described in this policy.

Your Rights and Choices

You have the following rights regarding your data:

  • Opt-Out of Analytics: Use browser settings or Google Analytics opt-out add-on
  • Opt-Out of Personalized Ads: Manage preferences at Google Ads Settings
  • Cookie Control: Manage or block cookies through browser settings
  • Data Privacy: Since we don't store your tool data, there's nothing to delete or modify

Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or legal requirements. We will post the updated policy on this page with a new "Last Updated" date. We encourage you to review this policy periodically.

Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:

Website: iloveutil.com

Email: Contact us through the website contact form

Frequently Asked Questions About Privacy

If my files do not get uploaded, how do the tools actually work?

When you select a file, your browser uses JavaScript APIs (specifically the File API and FileReader API) to read that file from your hard drive into the browser's memory. The processing code then runs locally—if you are compressing an image, the compression algorithms execute on your device's CPU using Canvas APIs and image encoding libraries. When processing finishes, the browser creates a Blob (a binary data object) containing the result and triggers a download using the download attribute on a dynamically created link element. All of this happens client-side. The server never receives or processes your files.

Can I verify that my files are not being uploaded?

Yes, absolutely. Open your browser's developer tools (usually F12 or right-click and "Inspect"), go to the Network tab, and watch what happens when you use a tool. When you select and process a file, you will see no POST requests uploading data. The network activity will be quiet except for perhaps ads loading or analytics pings (which do not contain your file data). If you are really paranoid, you can even use a network monitoring tool like Wireshark to inspect all traffic leaving your computer—you will see no uploads containing your file contents.

What about Google Analytics and AdSense? Do they see my files?

No. Google Analytics tracks page views, button clicks, and site usage patterns—it knows someone visited the PDF merger page and clicked the merge button, but it has no access to what PDFs you selected or what was in them. Google AdSense tracks ad impressions and clicks to serve relevant ads and measure performance, but again, it does not have access to the files you process. These services run in separate contexts from the tool processing code and cannot read the File objects your browser creates when you select files.

Could you add server-side logging in the future and start collecting files?

Technically, yes—we could change how the tools work. But there would be no reason to do so. Our entire value proposition is privacy-first, client-side processing. If we started uploading files, we would need server infrastructure to handle that processing (expensive), storage for temporary files (expensive and risky), and we would lose the main feature that differentiates us from competitors. Plus, we would have to rewrite this entire Privacy Policy and probably lose the trust of our users. The business model (ads) works fine with the current architecture. We have no incentive to change it.

What happens if there is a security breach of your website?

A breach of our website could compromise the HTML, CSS, and JavaScript code we serve—someone could potentially inject malicious code into the site. However, because we do not store user files, a breach would not expose any documents, images, or data that users have processed through the tools. There is nothing to steal because nothing is stored. At worst, a breach could affect the integrity of the tool code itself, which is why we use HTTPS, keep dependencies updated, and follow security best practices for the website infrastructure.

Do you comply with GDPR, CCPA, and other privacy regulations?

The GDPR (European Union), CCPA (California), and similar laws regulate how companies collect, store, and process personal data. Because we do not collect or store the files you process through our tools, most of these regulations do not apply to that data—we are not data controllers for your files because we never have them. For the analytics and advertising cookies we do use (Google Analytics and AdSense), those services handle compliance, and users can opt out through browser settings or Google's opt-out tools. If you have specific compliance questions or concerns, contact us and we will do our best to address them.

Can I use these tools for HIPAA-compliant or legally sensitive documents?

We are not HIPAA certified or officially compliant with specific legal frameworks that require formal certification. However, the architecture of client-side processing means your files stay on your device and never reach our servers, which addresses many privacy concerns. That said, if you work in a highly regulated industry (healthcare, legal, finance), you should consult with your organization's compliance team before using any online tools, including ours. They may have specific requirements or prohibitions regardless of how the tools work technically.

How do I delete my data from your servers?

You do not need to because we do not have it. Your files process locally and never reach our servers, so there is nothing to delete. For analytics data (page views, site usage), that is anonymized and aggregated by Google Analytics— we do not have personally identifiable logs of individual users. If you want to prevent future analytics tracking, you can install the Google Analytics opt-out browser add-on or use browser privacy settings to block tracking cookies.

Our Commitment to Your Privacy

At iloveutil, we believe your data belongs to you. That's why every tool processes your files entirely in your browser—no uploads, no storage, no tracking of your content. We only use analytics and advertising cookies to improve our service and keep our tools free for everyone.