Documentation
Privacy model (client-side tools)
How Toolverse by RS handles data: browser-first processing, what we do not upload, and how that claim maps to product behavior.
Published 2026-07-14 · Updated 2026-08-04
Most tools on this site are designed so your payloads, tokens, and files never need to leave the device for core operations.
Client-side by default
- JSON, encoding, JWT decode, UUID, and hash tools run in the browser
- PDF merge/split/rotate/compress and related converters process files locally (dynamic import / worker path)
- We do not POST file bodies or JWT contents to an API for those tools
- Input and PDF size limits protect the tab from freezing on huge files
What this is not
Client-side processing is not a substitute for device security. Anyone with access to your screen or clipboard can still see pasted secrets. Prefer local files and clear the workspace when finished.
Full policy
Read the site privacy page for cookies, analytics, and any endpoints that may exist outside the tool workspaces (for example contact or newsletter forms).
Try these tools
JSON Formatter
Format, beautify, and minify JSON in your browser. Free, private, and instant - no upload to a server.
JWT Decode
Decode JWT header and payload in your browser - inspect claims without uploading tokens.
Hash Generator
Generate SHA-1 / SHA-256 / SHA-384 / SHA-512 digests of text with Web Crypto - fully client-side.
Base64 Encode / Decode
Encode UTF-8 text to Base64 or decode Base64 back to text - instantly in your browser.
Merge PDF
Combine multiple PDF files into one document entirely in your browser.
Frequently asked questions
Do tools upload my files?
Default tools process input in your browser. PDF and document utilities use local libraries or in-tab workers - file bodies are not POSTed to our API. See the privacy policy for logging and any future server features.