Privacy Policy

Last updated: October 5, 2026

1. Privacy by Design

At Toolkit360, we believe your data is yours. Most of our tools run entirely in your browser using WebAssembly and modern browser APIs. For those tools, your files, text, and data never leave your device. Every tool page shows how that tool processes data in its "Privacy & Processing" panel.

2. No Uploads to Our Servers

No Toolkit360 tool uploads your files to our servers. Heavier tools such as the Background Remover, the GLB Compressor and the PDF suite do their processing in your browser too.

  • The Background Remover downloads its AI model (4 to 42 MB) and AI engine from this site the first time you use it, and your browser keeps a copy for next time. Your photos never leave your device.
  • We do not sell your files or derived data.

3. Tools That Use Outside Services

Some tools talk to a third-party service directly from your browser. Each one says so on its page:

  • Currency Converter fetches exchange rates from exchangerate-api.com (only the currency code is sent).
  • The P2P tools use the public PeerJS server (0.peerjs.com) and Google's STUN servers to connect two browsers. Your files, code, and video usually go directly between the browsers; when a network blocks that, they pass through a PeerJS relay server, still encrypted in transit. The two people in a session can see each other's IP address.
  • YouTube Thumbnail Downloader loads images from YouTube's image servers.
  • The API testers send requests to the URLs you enter.
  • The PDF suite's optional AI assistant sends the text you ask about to the AI provider whose API key you add. The key is stored only in your browser.
  • The PDF suite's OCR downloads its engine and language data from the jsDelivr CDN the first time you use it. Your PDF stays in your browser.
  • Local AI tools download their model once from a public model host; your text stays in your browser.

4. Analytics & Error Reports

We use Google Analytics 4 to understand which tools are used and whether they work: page views, the first time you use a tool on a visit, whether a run succeeded, failed or was cancelled, and whether a result was copied or downloaded, with coarse details such as the output format, file size or an error code. It never receives the text, files, passwords or keys you use in a tool. Google signals and ad personalisation are turned off, and the analytics script loads only after you interact with the page or a few seconds after it opens. The feedback form separately collects what you choose to submit, as described below.

We also use Google Analytics to count visits and see which tools are used (for example, that a 3D model was compressed and by how much). It sets first-party cookies (named _ga) to tell visits apart, and Google uses your IP address to estimate your country without storing it. We have turned off Google signals and ad personalisation. Google Analytics never receives the files or text you work with. You can opt out with Google's opt-out browser add-on or by blocking cookies for this site.

When a page crashes, we may send a technical error report (error message, code location, browser type, and page address) so we can fix it. Error reports do not include the files or text you work with.

5. Local Storage

We use your browser's Local Storage to save your preferences, theme, favorite tools, and recent history. This data remains on your device and is not synchronized to our servers.

6. Feedback & Contact

When you rate a tool with "Yes, it's great", we save an anonymous rating with the tool, the page address and the site version. When you send the feedback or issue form, we save your name, email address and message with the same details. Both are stored in the maintainer's private Google Sheet (a Google service), and issue reports may also be emailed to the maintainer; if that sheet is unavailable, the form is delivered by email through FormSubmit instead. Please do not include passwords, API keys or sensitive documents. Emails sent directly use your email provider. GitHub issues are public.

If you have any questions about this Privacy Policy, please open an issue on our GitHub repository or contact us via LinkedIn.