Privacy
Local-first, plain language.
SimonOS is built so everyday utility work can happen in your browser. This page explains what stays local, what gets measured, and where third-party services enter the picture.
Tool inputs and files
Most SimonOS tools process data locally in your browser. Text conversion, JSON formatting, UUID generation, length conversion, timestamp conversion, image resizing, PDF merging, PDF compression, markdown export, and OCR are designed to run without uploading your input files to a SimonOS server.
Browser tools are still not a safe place for real secrets. Avoid pasting passwords, API keys, private customer data, or confidential documents into any utility site unless you have reviewed the code and understand the risk.
Analytics
SimonOS uses Umami Cloud to understand aggregate usage: page views, which tools are opened, whether a tool succeeds or hits an error, and small non-content metrics such as search query length and result count. The actual text you type into tools, uploaded files, JSON payloads, OCR images, and generated outputs are not sent as analytics events.
The Umami script is configured with do-not-track support and excludes URL search and hash fragments from analytics. It is there to show which tools are useful enough to keep improving.
API routes
SimonOS also exposes JSON API endpoints for universal tools. If you call those endpoints, the request body is sent to the Cloudflare Worker so it can return a JSON response. API routes are useful for scripts and experiments, but they are not meant for secrets or sensitive production data.
Third-party services
- Cloudflare serves the website and Worker routes for simon-os.com.
- Umami Cloud provides lightweight analytics.
- GitHub hosts the public feedback forms used for tool requests and bug reports.
- Google Search Console is used to submit the sitemap and monitor search visibility.
Questions or corrections?
Open a GitHub issue if something here is unclear or if a tool should explain its data flow more directly.