1. Tool-specific, not one-size-fits-all
Privacy information follows each tool's actual architecture. Local tools and tools that request public data or a URL you specify explain their boundaries separately.
Privacy & data handling✓ ✓ ✓ ✓ Common questions
Your content, handled as each tool actually works.
ToolkitLoop is a free, useful browser-first collection. We explain where data is processed, which features need a network and how to reach us—without replacing real boundaries with a blanket “never online” claim.
The short version: local-tool content stays on your device.
Tools that can safely run in the browser process work locally, including text counters, image resizing and most calculations. Raw input is not sent to a ToolkitLoop content-processing API; the relevant tool page says so directly.
2. Content data and usage data are different
Raw text, images, filenames, content fragments and hashes are not analytics-event fields. Google Analytics on production is used only for page visits and general interactions.
3. Networked features are disclosed
A feature that needs an external result is not described as purely local. Read the notice near the input first, and submit only a URL, domain or query you are entitled to use.
4. Contact and updates
For a privacy question, contact contact@toolkitloop.com. We update this page when processing materially changes; it is a product explanation, not legal advice for your jurisdiction.
Know the data path before you use a tool.
Does ToolkitLoop upload my text or images?
Many text, image and calculation tools process work directly in your browser. Each tool explains its actual processing model; a local-tool promise should not be assumed for every tool.
Why do some tools still need a network connection?
Features such as exchange rates, domain information or a media URL you choose to open need network access to return a result. The relevant tool explains that boundary near its input.
What usage data does the site collect?
Production uses Google Analytics to measure page visits and general interactions. ToolkitLoop's event implementation does not allow raw editor content, images, filenames, fragments or hashes.
How can I ask a privacy question?
Email contact@toolkitloop.com. We will respond based on the tool and type of data involved.