Privacy-first design

Local processing wherever the browser can do the job

Many ToolsFam utilities run entirely in your browser. JSON formatting, encoding, hashing, QR generation, image edits and many PDF operations use client-side JavaScript and browser APIs instead of uploading your input to a backend.

Some features cannot work purely inside the browser. API Playground may use a proxy to reach public APIs that block cross-origin browser requests. Website Screenshot uses a public page renderer because browsers cannot capture arbitrary third-party sites directly. Those pages should make the tradeoff clear.

Favorites, recent tools and some tool drafts may be stored in localStorage so your browser can restore your workflow. If you create an account, supported data such as synced favorites can be associated with your profile.

Good privacy also depends on good habits. Avoid pasting production secrets, customer records or privileged tokens into any web tool unless you understand exactly how that tool processes data.