Privacy and local file processing

Selected files and working results

File bytes, names, headings and cell values are used in the browser session to parse, inspect and transform the data. Working datasets and previews remain in page and worker memory. The application does not intentionally send those contents to its server, put them in a URL or save them in browser storage.

Your source file is not overwritten. Export creates a new download. Your browser or operating system handles the downloaded file; keep and delete it according to your own needs. Closing or resetting the workspace discards the application's in-memory session.

Website requests

Loading the website requires ordinary requests for its pages, scripts and images. The hosting provider can receive connection information such as an IP address, browser headers and requested URLs while serving the site. Local file processing is not a promise that visiting a website makes no network requests.

The hosting platform may serve browser security checks and use security or authentication cookies. The application's own code does not send selected files to those checks.

A private preview can require the hosting platform's sign-in and authentication cookies. Those access controls are separate from the workspace's file-processing code and its in-memory datasets.

Anonymous counts and advertising

The workspace can request a same-origin counting image containing only the product, language, a fixed event name (page view, engagement, tool start, successful comparison or download) and a traffic class. File names, headings, values, sizes, results and document text are never counting payloads. Counts are events, not unique people; an ordinary browser interaction is a candidate user signal, not proof of a real person. Test and known automated traffic are kept separate.

Do Not Track and Global Privacy Control disable these counts. Use #traffic=off to turn counting off in this tab, or #traffic=test for testing; only that fixed preference is kept in session storage. No visitor identifier is created. Hosting still receives ordinary connection details while serving the counting request. There is no advertising SDK or third-party advertising script in the workspace.

Examples and reports

Downloadable examples contain fictional data. A data export can contain the values you chose to process; handle it as you would the original file. The separate audit summary is designed to describe operations and counts without copying file names, headings or source values.

Working with sensitive files

Use files you are allowed to process, inspect the result, and follow your organization's handling requirements. Browser extensions, your device and software outside UsefulDock have their own access and policies.