Skip to content
hateitall

Privacy

This policy is short because there is little to disclose. Files are processed on your device and are never collected. The site uses Google Analytics to measure page visits; it has no accounts and no upload endpoint.

Last reviewed: July 22, 2026

What we collect

  • Page-visit analytics on public pages. Public directory and editorial pages use Google Analytics (gtag.js) and Vercel Analytics to understand which pages are visited and how the site is found. File-processing workspaces are excluded. Google Analytics receives standard usage data — pages viewed, referrer, browser and device type, and approximate location derived from your IP address — processed under Google's privacy policy, and it may set cookies to distinguish visits. Vercel Analytics collects aggregated page views and web-performance metrics without cookies, under Vercel's privacy policy.
  • Behaviour analytics on public pages. Public directory and editorial pages may use Microsoft Clarity. Clarity records interaction data — clicks, scrolling, and session replays of page activity — to build heatmaps and help us improve usability, under Microsoft's privacy statement. Clarity is not loaded on file-processing workspaces, so file previews and processing controls are outside session replay.
  • Nothing else. No accounts exist, so no names, emails, or passwords are stored. No server receives your files, because the tools process files inside your browser — there is no upload endpoint in this application.

Analytics is measurement of public directory and editorial pages, not of your files. File-processing workspaces do not load Google Analytics, Vercel Analytics, or Microsoft Clarity at all. Every tool also works normally when third-party scripts are blocked sitewide.

Like any website, the infrastructure that serves our static pages (HTML, scripts, fonts) handles standard web requests to deliver those assets. Those requests are how every website loads; they do not contain your files, filenames, or any content derived from your files.

What your browser stores

  • Theme preference: if you switch between dark, light, and system themes, your choice is saved in your browser's localStorage under the key hia-theme. It never leaves your browser.
  • No file content: we do not write your files, file-derived data, or outputs to localStorage or any persistent browser storage. When you clear a file in a tool or close the tab, the in-memory copies are released.
  • Analytics cookies and storage: the analytics services above (Google Analytics and Microsoft Clarity) may set their own cookies or storage entries to distinguish visits and sessions. These identify a browsing session, not you personally, and never contain your file data.

What we never send as data

The following are never transmitted to us, our analytics providers, or any server as data fields — by architecture, not just by policy:

  • File bytes, before or after processing
  • Filenames and file paths
  • File contents of any kind: text, spreadsheet cells, pixels, audio, or video frames
  • Metadata values read from your files (EXIF fields, document properties, and similar)
  • Passwords you enter to unlock protected files
  • Findings, redacted values, or verification details from any tool

The line we hold on measurement

Analytics event data is limited to non-content usage: page visited, generic output format, coarse size bucket, and interaction events. Anything content-bearing — filenames, exact values, text, findings, metadata read from your files — is never sent as an analytics field. Hashing content does not make it acceptable to collect, and we treat it the same as the content itself. Processing workspaces exclude session replay as well as event analytics.

Third parties

The third-party scripts on this site are the analytics services described above: Google Analytics, Vercel Analytics, Microsoft Clarity, and DataFast (privacy-focused page-visit analytics under its own policy at datafa.st). There is no advertising, no chat widgets, and no remote AI APIs. Fonts and processing engines are served with the site’s own assets.

Changes and contact

If this policy changes, the date at the top changes with it, and the changelog will note it. Questions: hello@hateitall.com. For security reports, see the contact and vulnerability reporting page.