Data and privacy — a plain-English explanation
How the client-side architecture works, what Google Analytics 4 collects, and why I can't see your files.
The privacy policy covers the legal side. This article explains the technical reality in plain English.
Why I can't see your files
ToolBrigade has no file processing server. When you upload an image or PDF, it goes from your disk into your browser's memory — that's it. The JavaScript running in your browser tab processes it locally and produces the output. The file never travels over the network. There's no server to receive it, no database to store it, no logs of what you processed.
This isn't just a policy — it's the architecture. Even if I wanted to see your files, the current setup makes it impossible. The only way to change that would be to rebuild the tools with a server backend, which would defeat the entire point.
What Google Analytics 4 does collect
I use Google Analytics 4 to understand how the site is used — which tools are popular, where traffic comes from, what devices people use. GA4 collects:
- Page views and navigation paths
- Session duration
- Device type (desktop/mobile/tablet)
- Browser and OS
- Country (not city or precise location)
- Referring URL (where you came from)
IP anonymisation is enabled, so your full IP address is not stored. GA4 does not collect your name, email, file contents, or anything you type into tools. It sets two cookies (_ga and _ga_*) to distinguish sessions.
You can opt out of GA4 tracking by using a browser extension like uBlock Origin or by enabling “Do Not Track” in your browser settings. Disabling analytics has no effect on any tool's functionality.
The suggest-a-tool form and Resend
If you use the suggest-a-tool form, the data you enter — tool name, description, category, and optionally your email — is sent to me via Resend (a transactional email service). That data is used only to read your suggestion and reply if you left an email. Resend retains email metadata (sender, recipient, subject, timestamp) for up to 30 days; the message body is not retained after delivery. The contact page uses direct mailto links and does not go through Resend.
The Currency Converter
This is the one tool that makes an external network request. When you click Convert, a request goes to api.exchangerate-api.com with the source currency code in the URL (e.g. /v4/latest/USD). Your amount, target currency, and everything else stays local. Only the source currency code is in the request.
Full details are in the Privacy Policy.