Privacy
Last updated: September 12, 2026
Production files
Inventory, BOM, open-job and incoming-purchase-order CSV files are processed locally in your browser. The validation build does not upload those files or scan results to the server.
Validation data we store
The server may store product-usage events such as page views, scan starts, scan completions, result downloads and paid-intent clicks. These events can include campaign attribution, scan counts and a random browser-session identifier. They do not include the contents of your production CSV files.
If you request early access or founding access, the server stores the work email you submit together with the validation intent and campaign attribution.
Purpose
Stored data is used only to evaluate whether this early product solves a recurring manufacturing-planning problem, improve the validation experience and contact people who explicitly request early or founding access.
Retention
This is a validation build, not a production SaaS. Validation leads and events should be kept only as long as needed to evaluate the experiment. The operating target is a maximum 90-day rolling retention for raw validation events after cleanup automation is deployed.
No sale of data
Validation data is not sold. Production CSV data is not collected by the server.
Operational caution
Material Readiness Scan is an experimental diagnostic tool. Always verify source data and results before making operational decisions.