Local by design, clear by default.
Every current OpenToolSuite public tool is marked LOCAL. Its visible text, values, or selected files are handled in the current browser session and are not uploaded to OpenToolSuite by that tool. We do not keep a server-side file queue for those tools.
Google Analytics 4 loads only after you choose Allow optional services. Until then, analytics storage stays denied. LOCAL-tool file contents are not sent to Google. Configured advertising also stays off until you allow it. Core tools work either way.
Some workspaces save drafts, recent tools, favourites, consent choice, or theme preference in your browser storage until you clear them. Clear site data if you shared a computer.
The contact form is the exception: the message you type is stored so the owner can reply. Do not include passwords, payment details, or private files there.
We do not sell LOCAL-tool file contents. Optional analytics, if allowed, is for understanding which public pages are used — not for building a profile from the documents you process. You can change the consent choice later from the privacy control on the site.
Owner-console routes are disallowed in robots.txt and served with noindex. They are not part of the public catalog. Ads.txt, if published, is a seller record for the configured AdSense publisher — not a claim that ads are shown before consent.
If a future SERVER or HYBRID tool is released, its page will say what is sent, why it is needed, and the deletion policy before you start. We will not silently change a LOCAL tool into an upload converter.
Questions about this policy: feroz@opentoolsuite.com. For how to verify local processing, read How it works and Why local.
Browse all tools · How it works · Why local · Guides · Contact