Privacy Policy
UtilityHub is built upon a fundamental architectural commitment: your files, data, and text remain on your device. This policy details the exact technical boundaries between client-side execution, browser storage, and standard web infrastructure.
1. Architectural Overview & Privacy Philosophy
UtilityHub is an open collection of client-side web utilities designed for developers, analysts, and everyday internet users. Traditional online file converters operate by transmitting your confidential spreadsheets, documents, or photos across the internet to remote cloud servers, storing them in temporary databases, processing them on server clusters, and returning the result.
UtilityHub rejects this paradigm. We believe the safest place for your private data is on your own device. Every utility on this website runs directly inside your web browser’s local sandbox runtime using standard Web APIs, Web Workers, and WebAssembly. We do not maintain a backend processing pipeline or database for user conversion payloads.
2. Information Processed Locally by the 10 Utilities
To verify our client-side claims, the table below documents the exact runtime mechanism for each of the 10 published utilities:
| Utility | Data Input | In-Browser Processing Mechanism | Network Transmission |
|---|---|---|---|
| JSONL to CSV Converter | JSON Lines (.jsonl, .ndjson, text) | FileReader API + in-memory JavaScript RFC 4180 parsing | Zero network requests |
| CSV Duplicate Remover | CSV/TSV spreadsheets | FileReader API + in-memory Set/Map deduplication algorithm | Zero network requests |
| Bulk Text Cleaner | Raw text and log dumps | Pure JavaScript string pipelines in memory | Zero network requests |
| URL Query Parser | URLs and query strings | WHATWG URL API in memory. Never visits or fetches the URL | Zero network requests |
| CSV Separator & Encoding Fixer | Delimited files and text | ArrayBuffer byte inspection + TextDecoder/TextEncoder | Zero network requests |
| Unix Timestamp Converter | Epoch numbers, ISO dates | Native JavaScript Date & Intl APIs in memory | Zero network requests |
| Regex Tester | RegExp patterns & test text | Isolated Web Worker with 1,000ms ReDoS watchdog protection | Zero network requests |
| Bulk Image Compressor | JPEG, PNG, WebP photos | HTML5 Canvas 2D + OffscreenCanvas multi-threaded Web Workers | Zero network requests |
| PDF Page Extractor & Splitter | PDF documents | In-memory binary copying via pdf-lib and client PDF.js rendering | Zero network requests |
| HEIC to JPG Converter | Apple HEIC/HEIF containers | libheif WebAssembly inside dedicated Web Worker | Zero network requests |
Volatile Memory Clearance: All inputs, uploaded files, and generated outputs reside strictly in volatile random-access memory (RAM) allocated to your browser tab. Closing or refreshing the browser tab immediately purges this data from system memory.
3. Ordinary Website Requests & Hosting Infrastructure
We strictly distinguish between client-side utility processing and ordinary web hosting infrastructure traffic:
Your files, spreadsheets, and text inputs never leave your device. However, fetching the web application itself over the internet requires standard HTTP/HTTPS communication between your browser and our static hosting provider (Cloudflare Pages edge network).
When you navigate to UtilityHub or load any page, edge servers automatically receive standard technical transmission metadata necessary to deliver the static HTML, CSS, JavaScript, WebAssembly, and font bundles. This transient infrastructure metadata typically includes:
- Internet Protocol (IP) address of the requesting client.
- HTTP User-Agent string (browser type, version, and operating system).
- Referrer URI (the referring web page, if provided by the client).
- Timestamp, timezone, and duration of the connection.
- Requested file path and HTTP response status code.
These infrastructure logs are generated at the edge network layer for standard operational purposes: preventing Distributed Denial of Service (DDoS) attacks, enforcing rate-limiting, and routing traffic to the nearest global data center. UtilityHub does not harvest, aggregate, or sell this infrastructure data.
4. Cookies & Browser Storage
We adhere to strict transparency regarding browser storage:
Cookies: None Used
UtilityHub sets zero cookies. We set no tracking cookies, no session cookies, and no third-party marketing cookies.
localStorage: 1 Setting
We store a single key: utilityhub-theme ("dark" or "light") to remember your chosen interface theme across visits.
Managing Local Storage: You can clear your browser storage at any time by pressing F12 (Developer Tools) → Application → Storage → Clear site data, or via your browser's Privacy settings. Clearing this setting will simply reset your theme to default dark mode.
5. Analytics & Advertising Status
Google Analytics and Google AdSense are planned future integrations. However, as of the effective date of this Privacy Policy, neither Google Analytics, Google Tag Manager, Google AdSense, nor any other third-party tracking or advertising script is configured, enabled, or loaded on UtilityHub.
Future Commitment: Before any analytics or advertising service is introduced, this Privacy Policy will be formally amended and republished. Users will receive explicit disclosures regarding data collection, cookie usage, and available opt-out mechanisms prior to script activation.
6. Indian DPDP Act, 2023 & DPDP Rules, 2025
The Indian regulatory landscape is governed by the Digital Personal Data Protection Act, 2023 (DPDP Act, 2023), enacted by the Parliament of India in August 2023, along with the Digital Personal Data Protection Rules, 2025 published by the Ministry of Electronics and Information Technology (MeitY).
Official Commencement & Phased Implementation: Under Section 1(2) of the DPDP Act, 2023, the provisions of the Act come into force on dates appointed by the Central Government via notifications in the Official Gazette. Operational requirements—including the establishment and functioning of the Data Protection Board of India, formal registration procedures for Data Fiduciaries, and the consent manager framework—are implemented through official commencement notifications issued by MeitY.
In-Browser Execution & Regulatory Classification: UtilityHub is intentionally engineered so that file conversions, data formatting, and text processing run locally within your browser tab's volatile memory. Utility inputs are not uploaded to, persisted on, or profiled by our infrastructure. However, statutory characterization (including whether or under what circumstances an operator qualifies as a Data Fiduciary or Data Processor under Indian law) remains subject to appropriate legal review and official regulatory guidance. UtilityHub aligns its privacy practices with the transparency principles of the DPDP framework without making premature claims of complete statutory immunity or exhaustive compliance certification.
7. User Rights & Grievance Redressal
To the extent applicable under data protection principles, users possess the right to:
- Inquire whether any personal data concerning them is maintained by the website.
- Request the correction or erasure of any voluntarily submitted contact information.
- Submit privacy-related questions, feedback, or grievance redressal requests.
Because we do not store your files, logs, or personal documents on remote servers, we cannot access, view, retrieve, or delete files you have converted on our site—they exist solely on your local device.
8. International Data Transfers
UtilityHub is accessible globally. However, because our utility processing algorithms execute on your device's local CPU, your conversion payloads are not transferred across international borders. Ordinary web requests to fetch the website are routed by global CDN edge networks to provide optimal latency.
9. Children's Privacy
UtilityHub is designed for general audiences, specifically software developers, data professionals, students, and office workers. We do not knowingly solicit, collect, or store personal information from children under 18 years of age.
10. Security & Client-Side Limitations
While in-browser processing eliminates data interception in transit between your browser and an application server, no software environment is completely immune to security threats. Your security when using UtilityHub depends fundamentally on:
- The integrity and security of your physical computing device.
- Maintaining an updated, patched web browser.
- Browser extensions installed in your environment, which may have permissions to inspect DOM elements. For maximum confidentiality with sensitive files, we recommend operating in an Incognito / Private window with extensions disabled.
11. Updates to This Privacy Policy
We may update this Privacy Policy from time to time to reflect functional updates, architectural evolutions, or regulatory changes. Any modifications will be published on this page with an updated "Effective Date" at the top of the document.
12. Contact Channel
If you have questions, feedback, or grievance redressal requests regarding this Privacy Policy or our client-side processing practices, please consult our official channels:
Please refer to our Contact Page for communication guidelines. Dedicated public support email addresses will be announced alongside production custom domain deployment.