What stays in your browser.
Different tools need different kinds of processing. Trefnio makes that distinction explicit instead of calling everything “local” when it is not.
Files stay on your device.
The browser editions below are designed to work on the data you select locally in the page and then create a local download:
- FileForge Web — XML and JSON editing/validation.
- ImageForge Web — compression, resize, conversion and batch processing.
- RenameForge Web — rename previews and renamed-copy/ZIP export.
- PDFForge Web — reading, merging, splitting and page organisation.
Trefnio’s web application code does not need to upload the contents of those selected files to the Trefnio Product Manager or Agent Board to perform those jobs.
Routing is network-based.
RouteForge cannot calculate real road routes entirely offline in the browser. Address searches, coordinates and routing requests pass through Trefnio’s secured RouteForge gateway and onward to the routing service.
- The OpenRouteService key is kept on the Cloudflare Worker, not compiled into the browser app.
- Route plans are not stored as Product Manager or Agent Board records by the RouteForge Web code.
- Standard network and platform logs may still exist at infrastructure providers.
Normal website measurement.
Trefnio uses Cloudflare infrastructure and Web Analytics to understand site use and keep the service running. These measurements are separate from the contents of files you open in the local-processing tools.
Browser and network providers can also apply their own normal security, caching and diagnostic behaviour.
Use the right tool for sensitive data.
For especially sensitive or regulated material, check your organisation’s policies before using any browser or third-party service. Route data is inherently networked; file tools are the better fit when local processing is important.