User-entered text is processed locally in the browser and is not sent to PrivyBox servers.
Privacy
Private tools. No cloud upload.
PrivyBox is built around simple browser-side tools.
No AINo runtime model calls
No accountsNo sign-up wall
Local-firstTool inputs are processed in your browser
How privacy works
Processing model by tool type
Numbers and dates are used locally for formulas. Generated results are displayed in the page and are not uploaded.
Hashes, URL transforms, JWT decoding and Base64 conversions run client-side. Tokens and URLs are not sent to analytics.
QR payloads and images are generated in your browser without external QR APIs. WiFi passwords stay inside your browser session.
Core rules
What PrivyBox does today
Tool inputs, generated results and selected files stay in your browser. PrivyBox does not upload or store them.
Google Analytics loads on the production site after interaction or 10 seconds to measure page visits and basic usage. When first-party click measurement is enabled, PrivyBox records privacy-preserving daily aggregates of meaningful navigation and CTA clicks. Tool engagement measurement keeps a random identifier in browser storage for up to one day and stores only its SHA-256 digest with the tool name, visible-tab active time and use/copy/download counts for up to 30 days. It uses no cookies, fingerprints, IP addresses or raw user agents, honours browser privacy opt-out signals, and never sends tool inputs, results, selected files, passwords, JWTs, QR payloads or URL parameters to analytics.
Future disclosure
If a future tool needs more
If a future tool ever needs upload or server processing, it must clearly say so before you use it.