Privacy

CSV checks, import-change previews, selected fixes, and CSV export run in this browser. The beta does not upload your CSV, filename, products, SKUs, prices, vendors, URLs, or other catalog values to a One Purpose Tools server.

The browser temporarily holds the data needed for the active task. Resetting, replacing a file, switching away from a tool, closing the tab, or completing a bounded operation releases the related application session data according to the flow. Downloads are files you choose to save on your device.

This beta does not configure an external analytics provider. The code contains a closed, off-by-default event boundary for aggregate actions such as starting or completing a CSV check, change preview, or local export.

Allowed event fields use fixed categories such as mode, coarse file-size or row-count buckets, severity counts, registered rule IDs, export artifact type, and downloaded, blocked, or failed outcomes. Catalog values, filenames, exact prices, URLs, messages, source rows, and exported content are not allowed analytics fields.

A cleaned Shopify CSV preserves catalog values, including values that begin with spreadsheet formula markers. The separate audit report applies a limited formula-neutralization policy for human review. No CSV defense works in every spreadsheet program, and the audit report must not be imported into Shopify.

Your browser, device, extensions, download folder, spreadsheet software, and any service where you later upload a file have their own security and privacy behavior. Review them before handling a sensitive catalog.

If the product later adds an analytics provider, account, payment system, or server feature, this page and the product design must be reviewed before that change ships.