Trust & transparency
How StayInBrowser Processes Your Files Locally
The website code arrives over the network. Your selected tool files and sensitive inputs then stay in browser memory or local browser storage instead of being uploaded to any server.
Your file and tool inputs are not uploaded to any server.
Browser-side processing
JavaScript coordinates each tool. Image tools use Canvas and browser codecs; specialist HEIC and TIFF support uses lazy-loaded WebAssembly or JavaScript decoders. PDF tools use bundled client-side PDF libraries. Large CSV parsing uses a Web Worker where the browser supports it.
Memory and browser storage
Most tools keep working data only in memory and discard it when you reset or close the page. The Private Spending Tracker is different: it intentionally stores financial records in IndexedDB on the current device so they remain available between visits. You control exports and backups.
Loading a website is not uploading your file
Your browser must request HTML, CSS, JavaScript, fonts, and other site assets from the web host. Hosting infrastructure can receive normal connection details such as IP address and request headers. Local tool processing does not add your selected file contents or pasted tool inputs to those requests.
Limits of local processing
Browser memory, CPU speed, format support, and device temperature all matter. Very large images or PDFs can be slower on mobile devices. Some codecs depend on the browser and operating system, encrypted PDFs may not open, and a tab can still lose unsaved work if it closes.