Privacy
Your files and tool inputs stay in your browser.
Tool files and sensitive inputs are processed locally inside your browser.
For local file and input tools
Your selected images, PDFs, text, CSV, JSON, YAML, JWT, Base64, SQL, media, recordings, QR payloads, invoice details, calculator values, filenames, settings, metadata, and generated results are not uploaded to any server. Tool work happens inside your browser.
For the Private Spending Tracker
Transactions, amounts, budgets, merchant names, account labels, notes, tags, imported CSV data, and backup contents are processed and stored in your browser on this device. The tracker does not upload those financial records to any server. Clearing browser or site data can remove local records, so you should keep your own backups.
Specialist decoders are local too
Image, PDF, OCR, data, and media routes download their JavaScript, WebAssembly, codec, model, or worker engines as ordinary website code only when needed. Your selected input is passed to that code in browser memory and is not uploaded to any server.
What the website still needs
Like any website, the application files themselves—HTML, CSS, and JavaScript—must be delivered to your browser by the web host. Normal hosting infrastructure may receive standard connection information such as an IP address and request headers.
No advertising or application backend
This release has no advertising, authentication, analytics script, application database, monitoring service, or application backend.
Contact and feedback email
Contact and feedback links open your own email application. Information you deliberately include in a message is handled by your email provider and is separate from local tool processing.
The durable promise
Every public tool is designed so that selected files and sensitive tool inputs stay in the browser. If hosting or other website infrastructure changes in the future, this page will distinguish those normal website requests from tool-file processing.
Last updated: August 9, 2026