PRIVACY

Your work stays yours.

The public information site and the file-processing workbench have separate roles and separate security policies.

Files and local processing

The workbench selects and processes local spreadsheets and creates fresh exports in the browser. It has no upload endpoint, analytics integration, session recording or advertising. Do not send confidential files to the project for support or evaluation.

The local processing boundary

Spreadsheet content stays within the browser during local inspection and comparison. File names, sheet names, column names and cell values must not be sent as analytics or placed in URLs or browser storage.

Ordinary site requests

Opening a website sends ordinary requests to its hosting provider, including connection metadata such as an IP address. Browser-local file processing does not mean visiting the website creates no network traffic.

Public site visit and performance statistics

Canonical pages on tools.chernconsulting.com use Cloudflare Web Analytics for visits, referrers, browser information and page performance. Requests go to Cloudflare and include ordinary connection metadata; Cloudflare states that it discards IP addresses at the edge and does not use cookies or browser storage for this service. The loader skips pages with URL parameters, fragments or a non-canonical referrer path. The workbench, Preview and 404 pages do not load this analytics integration. No custom tool events, filenames, worksheet names, keys, cell values or file contents are supplied. There are no advertising, recording or heatmap integrations.

Voluntary email feedback

If you send an email to the published feedback address, the project recipient receives your sender address and the message you choose to provide. Gmail processes and stores that email. Email is separate from browser-local file processing; the mailto link does not attach working files, parameters or results. Describe general steps or synthetic examples without sensitive workbooks, internal screenshots, personal data, passwords or API keys.

Future changes

Any future cloud-save feature or third-party integration requires a separate product and privacy review. Changes to the current data boundary will be described here before they are introduced.