Local-first by default.
Simply Tools is built so core tasks can run in your browser. This page explains how local-first tool input, Cloudflare or hosting security layers, Vercel Analytics, browser-side storage, cache, and direct inquiries are handled today.
Page briefing
Privacy at a glance
The main goal is straightforward: keep core tool input local, keep site analytics narrow, and avoid turning everyday utility work into a tracking-centered experience.
- Core tool input is designed to stay in the browser whenever the workflow allows it.
- Site analytics should stay limited and never include the contents of your tool input.
- Cloudflare or similar edge layers may still handle delivery or abuse protection.
- Some convenience features may store local drafts, history, or cache data on your device.
Last updated: June 28, 2026
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 [email protected], 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.
6. No third-party ad tracking today
Simply Tools does not currently use third-party ad pixels, retargeting tags, or cross-context behavioral advertising cookies on the public site. If monetization changes later, the policy should be updated before those tools go live.
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.
9. Contact and privacy requests
For privacy questions, support requests, legal notices, or general inquiries, contact [email protected].