Browser-based and server-based processing boundaries
Understand the difference between local file computation, dependency downloads and account or service requests.
Draft prepared: 2026-10-02. Publisher: GXA Technologies. No named expert review is claimed. AI-assisted draft; human editorial review pending
Local computation is a specific claim
A browser can read a selected file into memory and run JavaScript or WebAssembly against its bytes. The file picker granting access is not itself evidence of an upload; a subsequent request carrying the file would be.
Many GXA file tools follow this local pattern. That does not mean the website makes no network requests, works offline from first load or needs no third-party resources.
Different requests carry different information
Downloading an OCR model or PDF library brings code or data into the browser. Saving processing history can send a filename, size, tool and status to the application server. Loading analytics or advertisements is another network boundary.
GPS Map Camera has a distinct boundary: location lookup and map services require location-related requests. Read its disclosure rather than applying the generic local-file description to every route.
Choose according to the file and the device
Local computation avoids a file-processing upload in the documented workflow, but it uses the device’s memory and CPU. A large scanned PDF or segmentation model may overwhelm a small phone. A server workflow may have different capacity but requires a clear transfer and retention policy.
For sensitive material, decide whether the whole website and browser environment meet your requirements, including extensions, account history and clipboard use. Local processing alone is not a security certification.
Investigate boundaries without leaking a real document
Use a harmless test fixture when inspecting network behavior. Check requests during selection and processing rather than only during page load. Distinguish library requests from payloads that contain filenames, text, coordinates or file bytes.
Do not send a private file to support to ask whether it stays private. Report the route and observed behavior without credentials or source content.
Report an error in this information
Include the page address and the statement that needs checking. Do not send private files or credentials.