Local-first by default.

1. Core tool input stays local by default

Simply Tools is designed so core browser workflows can run on your device. For supported local-first tools, we do not intentionally send your working files, pasted text, images, or intermediate results to our servers for conversion, formatting, or inspection.

2. Contact and support information you send us

If you email contact@simply-tools.com, we may receive your email address, message contents, attachments, screenshots, and any other information you choose to include so we can respond to support, privacy, legal, or business questions.

3. Limited analytics and product usage data

We use Vercel Analytics and a narrow set of first-party product usage events to understand traffic, performance, reliability, and broad feature usage. Those events are intended to describe actions such as opening a tool, copying, downloading, or using catalog search without including the actual contents of files, pasted text, passwords, tokens, or generated outputs.

4. Hosting, security, and supporting assets

Site delivery and abuse protection may rely on Cloudflare as well as hosting and edge infrastructure. Some browser-side libraries may also fetch supporting assets such as worker scripts from trusted CDNs. That is separate from the contents you process inside a tool, which are still intended to stay in-browser unless a tool explicitly states otherwise.

5. Browser-side storage and cache

The site uses browser storage for convenience features such as theme preference, favorite or recent tools, and some tool drafts or histories. A service worker may also store static assets or page responses in Cache Storage to improve repeat-load or offline behavior. This data stays on your device until your browser clears it or you remove site data. No method of transmitting data over the internet can be guaranteed to be risk-free, so we cannot promise the absence of all risk.

6. Third-party advertising and monetization

Simply Tools is free to use and supported by displaying non-intrusive standard banner advertisements through third-party ad networks, primarily Adsterra. In jurisdictions requiring consent (such as the EEA, the UK, and Switzerland), third-party advertising scripts and cookies are only loaded after you explicitly grant consent via our cookie banner. We decide whether your region requires consent from the country code of the incoming request, classified once at the edge of our hosting network and remembered in a one-year region preference cookie; no behavioural profile is built, and you can always make an explicit choice yourself. In other regions, you may opt out or modify your choices at any time using the advertising choices section at the end of this page. Importantly, your tool inputs (such as files, pasted text, passwords, or tokens) are processed locally in your browser and are never shared with or sent to advertising partners. Where the law requires consent for advertising processing, the legal basis is your consent; elsewhere we rely on our legitimate interest in running a free, ad-supported service, which you can object to at any time. If your local law treats sharing identifiers with advertising partners as a "share" for cross-context advertising (as in California), the advertising choices section below is your opt-out — we do not sell personal information for money. For more details regarding how advertising data is processed, see:

Adsterra Privacy Policy

7. Accounts are not active today

A public account system is not active on the core site today, and Clerk is not currently in use. If account features are introduced later, we may add an identity provider and update this page and the Cookie Policy at that time.

8. Your local environment still matters

If you handle highly sensitive material, remember that browser extensions, compromised devices, screenshots, shared machines, and your own browser environment remain outside the scope of product-side privacy guarantees.