Frequently Asked Questions

No. Every tool on BoltQuickTools runs entirely in your browser using standard Web APIs (Canvas, Web Crypto, FileReader). Your inputs (text, images, files, credentials) never reach my servers. You can confirm this yourself: open browser DevTools, switch to the Network tab, then use any tool. If a tool were uploading your data, you would see the request. There is no such request.

For the full technical explanation, see my essay on the client-side architecture or the privacy policy.

Three categories of cookies:

• Strictly necessary: a single value (cookie-consent) that remembers your accept/reject choice so the banner does not reappear.
• Advertising: Google AdSense sets cookies for ad delivery and fraud prevention. The ad script is only loaded after you choose Accept, so rejecting the banner keeps these cookies off your browser.
• Functional: small localStorage values (recent tools, randomizer counters, language preference). These stay on your device.

The consent banner gives every visitor an explicit accept/reject choice, and the Google ad script stays blocked until you accept. You can change your decision at any time with the Cookie settings link in the footer. We plan to adopt Google's certified Funding Choices CMP (IAB TCF) for EU/UK/Swiss visitors once AdSense review completes. Full legal-basis breakdown is in the privacy policy, section 5.

I have no data to delete because I never collected any. For data held by my third-party services (Google AdSense ad data, Cloudflare security logs), use their data-request portals directly.

Yes, all 115 tools are completely free with no usage limits, no sign-up, no email capture, no "premium" upsell. The site is supported by Google AdSense advertising. The tools themselves will always be free to use.

Most tools work offline after the initial page load, because all the code is contained in one HTML file. A few tools (OCR, image upscaler) fetch additional WebAssembly resources from a CDN on first use; those tools need network on first load but work offline afterward.

Email [email protected]. Bug reports get priority. Include the tool URL, your browser and OS, and what you expected to happen versus what did happen. Most bugs get a fix the same evening.

Either I have not built it yet, the meta is too volatile to maintain accurately, or it would not work entirely client-side. Email me with your suggestion. If enough people ask and the game has a stable enough roster, I add it.

The Content Security Policy includes unsafe-eval because the Google Translate widget and a few crypto libraries need it. This does not mean the site executes arbitrary code on your data. The CSP also restricts which origins can be loaded; the full policy is visible in the response headers.

Linking is encouraged. iframe-embedding is not blocked, but I recommend direct links so users see updates. If you have a specific embedding use case, email me to discuss.

Within 5-10% of the exact tokenizer output for English prose. For exact counts on OpenAI models, use the official tiktoken library or OpenAI's tokenizer page. For Claude, Anthropic does not publish their tokenizer, so all third-party estimates (including mine) are approximations. See the LLM cost-control post for details.

The hosting bill is real but small (about $2/month for Cloudflare-fronted nginx). Ads cover it. The privacy commitment is about your tool data, not about your visit to the site. Google AdSense sees your visit; it does not see what you paste into the tools.

ca-pub-4867472068718268. This is also published in /ads.txt per the IAB standard, which prevents ad-revenue spoofing.

No. Only Google AdSense. No affiliate links, no sponsored posts, no paid placements anywhere on the site.

nginx serving static HTML behind Cloudflare. No JavaScript framework. No bundler. A Python script generates the homepage, category pages, sitemap, and OG metadata. Each tool is a single hand-written HTML file. See the architecture post for the deep dive.

The HTML and JavaScript are publicly viewable for every tool (browser View Source). The build scripts and content are not in a public git repository today. I am considering open-sourcing parts of it; let me know if that would be useful.

Not yet. If there is demand, I will add one for the blog. Email me and let me know.

The most useful support is using the tools and telling people about them. If you find a stale gaming randomizer roster or a bug in a tool, email me; that saves me debugging time and helps the next user. There is no donate button.