File Privacy
Last reviewed: 24 September 2026
For browser-local tools, selected file contents stay in the browser processing path.
Selected files
prvkit application code does not intentionally upload selected file contents to the origin server for processing. Images and PDFs are decoded or transformed in browser memory. Generated results use local browser objects and Blobs until you download them or leave the page.
OCR and metadata
SafeShare OCR text, detected GPS data and supported image metadata remain browser-local. PDF processing and page rendering also remain browser-local. Filenames and file contents are not intentionally written to server URLs.
Application assets and network requests
The browser still requests the website, code, models, WASM and PDF.js assets from the site infrastructure. Those asset requests can expose ordinary network data, but they are not APIs that receive the selected file.
Practical limits
Local processing does not make a device or browser immune to malware, extensions, shared-device access or downloaded-file exposure. Review results before sharing and manage downloads on sensitive devices.