Privacy Policy

Your media files are never sent to us. All compression and conversion happens inside your browser using WebAssembly. We operate no upload endpoint and no storage for your files, so there is nothing for us to read, keep, or lose. The page instruments its own network layer and shows the result in the privacy meter: the only requests that leave your browser are ones the page makes to load itself.

We do not collect your name, address, IP-based profile, or the contents, names, sizes or metadata of the files you process. We do not use advertising cookies, tracking pixels, session recording, or third-party analytics of any kind — the browser security headers this tool needs in order to run the encoder would block such a script anyway.

We do keep one first-party counter, described below. It has no cookie and no identifier, it cannot be joined to a person, and blocking it costs you nothing.

• Loading the site. Our host serves the page, the encoder and the fonts. Standard server logs (IP address, user agent, requested file, timestamp) are produced by the host and retained for a short period for security and abuse prevention.
• An anonymous counter. A request of a few dozen bytes records that a page was viewed, that a checkout or activation button was pressed, and that some number of batches ran. It carries no cookie, no identifier and nothing about your files, and the counts expire on their own. The privacy meter reports it separately from uploads so the number it shows for your media stays honest.
• Verifying a licence key. Nothing. Keys carry their own signature and are checked inside your browser, so pasting one sends no request at all — it works with the network switched off.
• Redeeming a code. The one exception to the line above. A redeem code — the kind issued for a review copy or a giveaway, not one bought at checkout — is sent to us so we can confirm it exists, mark it used and sign a licence key back. We record that the code was spent, when, and the country your request came from; we do not ask for or store an email address for it. After the exchange the key behaves like any other and is never checked again.
• Buying a licence. Checkout is handled by Waffo.com Limited, our reseller of record. They collect the payment details and billing information needed to complete the sale and to meet tax obligations. We receive only your email address and the fact that a licence was issued. We never see your card number.
• Sending feedback. If you use the feedback form, the message you typed — plus an email address, only if you chose to give one — is sent to us so we can read and reply to it. Nothing else about your session is attached.

Two things, both in your browser’s localStorage. If you buy a licence, your licence key is stored so you do not have to re-enter it. Your chosen interface language is stored so the page opens in it next time. Your processing settings are not stored: they reset when you reload. This data stays on your device; clearing your browser storage removes it.

Where the GDPR or UK GDPR applies, we process the limited data above on the basis of performing our contract with you (issuing and verifying a licence) and our legitimate interest in keeping the service available. You may request access to, correction of, or deletion of the data associated with your licence at any time by writing to [email protected]. Because we hold so little, such requests are usually resolved by deleting your licence record.

BatchCrunch is a general-purpose utility and is not directed at children under 13. We do not knowingly collect data from them.

If this policy changes materially we will update the date above and, where the change affects licence holders, note it in the release notes. Continuing to use the service after a change means you accept the revised policy.

Questions about this policy: [email protected]. We reply within two business days.