Privacy by design
Toolbito is designed so supported calculations, text operations, code utilities, and file conversions run in your browser whenever practical. This page documents the boundary precisely: what stays local, what operational metadata may be sent, what third parties can receive, and what users should still avoid entering.
Processing boundary
Ordinary values entered into supported tools are processed by client-side JavaScript. Toolbito does not need an account profile or a server copy of those values to produce the result. A feature that cannot meet this boundary must identify the upload before processing; it must not silently reuse the local-processing claim.
Operational analytics
Analytics events may contain the service and tool identifier, event name, anonymous session identifier, locale, page path, device class, viewport dimensions, duration, success state, and a bounded error code. They must not contain input text, numbers entered by the user, file contents, result text, URLs pasted into a tool, tokens, or direct personal identifiers.
Browser storage
Favorites, recent tools, and selected presets can use localStorage or sessionStorage on the current device. This data is controlled by the browser, is not an account sync feature, and can be removed with browser site-data controls. Shared devices should be treated as shared storage.
Files and generated downloads
Supported image, document, data, and archive operations use browser APIs and local libraries. Generated downloads remain under browser and operating-system control. Keep the original until you have opened the result and checked dimensions, page order, encoding, metadata, and visible quality.
Third-party and advertising boundary
Toolbito can load disclosed third-party assets such as advertising scripts. Those services operate under their own policies and consent signals. Tool input values must never be inserted into ad requests, analytics payloads, URLs, page titles, or logs. Advertising being present does not change the local-processing promise for the tool itself.
Safe-use limits
Do not paste passwords, production access tokens, private keys, regulated personal data, confidential contracts, or unreleased source code. Client-side processing reduces server exposure, but it does not protect against a compromised browser extension, shared device, screen capture, clipboard history, or malware.
How we verify the claim
Release checks inspect network requests during representative tool use, validate the event allowlist, confirm that file tools do not create upload requests, and scan pages for unexpected endpoints. New features should fail closed: if their processing boundary is unknown, they do not receive the privacy badge until reviewed.
Questions and corrections
If a tool behaves differently from this document, stop using it with sensitive material and report the route, browser, and observed request through the contact page. Do not include the sensitive input in the report.