Privacy Policy

Last updated: June 2026

1. Privacy‑First Architecture

Utilify is engineered from the ground up as a privacy‑first platform. Every tool operates exclusively inside your local web browser using native JavaScript and, where applicable, compiled WebAssembly modules. When you upload a file or paste text into any Utilify utility, that content is read into an ephemeral, in‑memory block that exists only for the lifetime of your current browser tab.

No file contents, text inputs, generated outputs, or processed metadata ever leave your device. There is no background upload queue, no cloud sync layer, and no remote processing pipeline. Once you close the tab or refresh the page, the ephemeral memory block is released by the browser's garbage collector and is unrecoverable.

2. No Remote Data Streams or Third‑Party Tracking

We do not operate remote file repositories, CDN ingestion endpoints, or edge processing nodes for the core utility engine. Because every conversion, encoding, decoding, and transformation is computed on your own CPU, there is no network egress path for your data to be observed, logged, or intercepted by Utilify or any intermediary infrastructure.

We do not embed third‑party social widgets, fingerprinting scripts, or behavioral trackers that monitor file names, operation types, or result sizes. Our analytics layer is intentionally minimal and operates only on anonymized page‑level signals such as viewport dimensions, country‑level GeoIP, and aggregate tool popularity counters.

3. Data We Explicitly Do Not Collect

File contents — binary blobs, text streams, images, audio, video, or document markup processed through any tool.
File metadata — original file names, MIME types, creation timestamps, EXIF tags, or size identifiers.
Personally identifiable information — names, email addresses, phone numbers, physical addresses, or government identifiers.
Account credentials — we do not offer user accounts, authentication flows, or password storage.
Clipboard contents — we do not silently read or transmit your system clipboard.
Local storage data — we do not persist tool inputs or outputs in browser localStorage, IndexedDB, or Service Worker caches.

4. Cookies & Programmatic Optimization

Utilify uses cookies and similar storage tokens strictly for non‑identifiable browser configuration analytics and programmatic optimization through advertising channels such as Google AdSense. These cookies do not store file data, personal identifiers, or cross‑site browsing histories.

Their sole purpose is to enable aggregate reporting metrics — such as approximate geographic distribution, device category breakdowns, and anonymized ad impression validation — so that we can continue to fund free utility hosting without ever monetizing your personal data.

You may disable cookies via your browser settings or through the standard consent management banner presented on your first visit. Disabling cookies will not impair the functional operation of any tool.

5. Aggregate Analytics

We maintain a privacy‑respecting analytics pipeline that records only high‑level, non‑identifiable telemetry: page load events, tool category selection, scroll depth, and generic error rates. This telemetry is stripped of IP addresses, User‑Agent strings, and any data that could be reverse‑engineered into a personal profile.

Ad partners receive only the standard HTTP request headers inherent to any web page load (e.g., language preference, coarse geolocation). They do not receive your files, your processed outputs, or any behavioral data tied to individual tool usage patterns.

6. Questions & Contact

If you have any questions about this Privacy Policy, our data practices, or the technical architecture that protects your information, please reach out through the contact page and we will respond as promptly as possible.