Filehinge
← Index

Privacy

What we record, what we do not, and how to check.

Your file

The file you drop never leaves your browser. There is no upload step. Code and the occasional WebAssembly binary stream from our CDN to your tab; the conversion happens there. The output is created in memory and saved through the File System Access API or a download link.

You can verify this. Open DevTools (F12), switch to the Network tab, drop a file, and watch the requests. The only traffic is for our own assets.

What flows where

Solid arrows are real network traffic. The dashed line is what the browser will not do because our Content Security Policy refuses to let it.

Filehinge data-flowYour browser tabYour file(input)Output blob(in memory)Web Worker (no network access)decode → process (WASM / WebGPU)→ encode → return BlobCSP forbids any cross-origin fetchfrom this worker context.Filehinge CDN (Cloudflare)HTML, JavaScript, CSS,fonts, WASM (SHA-256 pinned),PWA manifest, /manifests/*.jsonread-only, immutable, no upload endpointassetsAny other serverthird-party converters,analytics that read file content,ad networks, anything elseblocked by Content-Security-Policyblocked

Analytics

Plausible Analytics in cookieless mode. Plausible counts page views and four custom events: conversion_started, conversion_completed, conversion_failed, and the upgrade clicks. Sizes and durations are bucketed; filenames and content are never sent. No cookies, no cross-site tracking. Block our Plausible script and the app still works.

Cookies

We do not set any. No accounts, no cart, no server session.

Local storage

We cache verified WebAssembly binaries in your browser's Origin Private File System so you do not re-download them on every visit. Local to your browser; not readable by other sites.

Contact

Email info@filehinge.com if a claim on this page does not match what you observe.