Local browser processing
Many tools read files with browser APIs and generate outputs in memory, then offer a direct download.
Technical trust center
How NivaTools processes files, text and generated content
Privacy at NivaTools is not only a legal promise. It is a technical design choice: whenever possible, tools run directly in your browser using local JavaScript, the File API, canvas, blobs and downloadable outputs instead of account-based cloud storage.
No account required
No server file storage
Browser-first architecture
Tool-specific limits
Last updated: July 2, 2026
Architecture, not slogans
Local workflows are the trust layer
NivaTools is designed for fast everyday tasks where users can process files, text or generated outputs without creating an account or storing work in a NivaTools dashboard.
No NivaTools file vault
The current public tools are not built as cloud storage, project history or user account systems.
Honest external library notes
Some tools load trusted client-side libraries such as pdf-lib or SheetJS. The files remain in the browser workflow.
Processing matrix
What happens in each NivaTools tool
This matrix explains what runs locally, what external scripts are loaded, whether uploads are required and whether NivaTools stores user data on a server.
| Tool | Local processing | External library loaded | Upload required | Server storage | Technical note |
|---|---|---|---|---|---|
| Invoice Generator | 100% local Invoice fields and PDF generation run in browser JavaScript. |
None beyond NivaTools static JS. | No. | No. | PDF output is generated as a browser Blob. Users must store their own invoice records. |
| Image Compressor | 100% local Images are decoded and re-encoded with browser canvas. |
None beyond NivaTools static JS. | No. | No. | Canvas export commonly strips original metadata because the image is re-rendered. |
| CropNiva | 100% local Cropping, preview and export happen in the browser. |
None beyond NivaTools static JS. | No. | No. | Large images can use more device memory because editing happens on the user device. |
| QR Code Generator | 100% local Text, links, Wi-Fi data, vCards and events are encoded locally. |
None beyond NivaTools static JS. | No. | No. | NivaTools does not track generated QR links or store QR contents. |
| PDF Toolkit | Browser-side PDF files are read and processed in browser memory. |
pdf-lib from jsDelivr CDN. | No. | No. | The browser requests the PDF library script, but selected PDF files are not uploaded by this static tool. |
| OmniDoc Converter | Browser-side Supported text, data and spreadsheet workflows run client-side. |
SheetJS from cdn.sheetjs.com for spreadsheet parsing. | No for supported current workflows. | No. | Advanced PDF input, ODT and EPUB conversions are intentionally limited until a reliable future engine exists. |
| Image Converter | 100% local Image format conversion uses browser canvas and Blob downloads. |
None beyond NivaTools static JS. | No. | No. | Animated GIFs may be treated as a static frame depending on browser decoding. |
| GifCraft Studio | 100% local Frames are loaded, previewed and encoded in the browser. |
None beyond NivaTools static JS. | No. | No. | Large frame sets can be slower because generation uses the user's device resources. |
| Text Tools Suite | 100% local Text cleanup, counters, case changes and slug generation run in browser JS. |
None beyond NivaTools static JS. | No. | No. | Avoid pasting passwords, private keys or confidential text into any web page unless necessary. |
| UltraPassword Maker Web Free | 100% local The free 16-character generator runs in the browser. |
None beyond NivaTools static JS. | No. | No. | Generated passwords are not saved by NivaTools. Users must store them securely. |
| UltraPassword Maker Full for Windows | Offline app The premium desktop app runs on Windows, including portable USB use. |
No web library needed while using the app offline. | No. | No. | The Windows app is separate from the website and is intended for local/offline password generation. |
Important: NivaTools is not a legal, compliance, security-audit or backup service. For highly confidential, regulated or business-critical files, choose the workflow that matches your risk level.
What local means
Your browser becomes the workspace
When a tool is marked local or browser-side, the selected files are handled by the browser runtime on your device. NivaTools does not provide a user dashboard, permanent file library or server-side archive for those outputs.
Files are read by browser APIs
Tools use features such as file inputs, FileReader, canvas, array buffers and object URLs to create outputs.
Downloads are generated in memory
Outputs are commonly created as Blob objects and downloaded directly by the browser.
External scripts are disclosed
Where a client-side library is loaded from a CDN, the page explains it clearly in the matrix.
Technical FAQ
Advanced privacy and processing questions
Are my files uploaded to NivaTools servers?
For the current browser-first tools described on this page, uploads are not required for the supported workflows. Files are selected and processed in the browser, and NivaTools does not store them in a server-side account.
Does PDF Toolkit read my PDFs?
The PDF file is read by your browser so the selected operation can run. PDF Toolkit loads the pdf-lib client-side library from jsDelivr, but the selected PDF file is not uploaded by this static tool.
Why does OmniDoc load SheetJS?
SheetJS is used client-side to parse spreadsheet files in the browser. The spreadsheet file is handled locally for supported workflows; the library request is separate from the file contents.
Does NivaTools use localStorage or browser storage for my files?
The current tools are not designed to save uploaded files, generated invoices, QR contents or edited images in localStorage, sessionStorage or IndexedDB as a file history. Outputs should be downloaded and stored by the user.
Are generated downloads stored after I leave the page?
No. Browser-generated Blob URLs and in-memory outputs are temporary. Once the page is cleared or closed, users should rely on the files they downloaded to their own device.
Is browser-first the same as fully offline?
No. Browser-first means the processing happens in your browser where possible. Some pages may still load website assets, ads or client-side libraries from the network. UltraPassword Maker Full for Windows is the offline desktop option.
Can metadata remain in exported files?
It depends on the tool and file type. Canvas-based image exports often remove original metadata because they re-render pixels, while PDF workflows may preserve or change metadata depending on the operation and library behavior.
Should I process sensitive legal, medical or financial documents online?
Use caution. Even with browser-side processing, highly sensitive or regulated files may require an offline, audited or professional workflow.