Local-first by default.
Simply Tools is built so core tasks can run in your browser. This page explains how tool input, optional sign-in, cookies, and limited site analytics are handled.
Page briefing
Privacy at a glance
The main goal is straightforward: keep core tool input local, keep account handling separate, 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.
- Sign-in is optional and handled separately from core tool use.
- Site analytics should stay limited and never include the contents of your tool input.
Last updated: April 2026
1. Core tool input stays local
For core browser tools, the text or file you use is processed on your device. We do not intentionally send that working input to our servers for conversion, formatting, or inspection.
2. Optional sign-in is handled by Clerk
If you sign in, session and identity handling are managed by Clerk. That may include your email address, profile details, and the cookies needed to keep the signed-in session working securely.
3. Limited site analytics and operations data
The site may use limited analytics or operational telemetry to understand broad traffic patterns and keep the product stable. This is separate from the actual content you process inside the tools.
4. Your local environment still matters
If you handle highly sensitive material, remember that browser extensions, local device compromise, screenshots, and shared machines remain outside the scope of our product-side privacy guarantees.