CatalogWash
Privacy Policy
CatalogWash is built around browser-first catalog cleanup. This page explains what is processed locally, what may be sent to the backend, and what is not stored by default.
Browser-first file processing
CSV/XLSX files are processed in your browser by default. CatalogWash does not upload or store the full supplier file unless a future feature explicitly asks for that permission.
AI mapping and saved sessions
AI mapping sends only column headers and a small sample after you click the AI mapping action. Saved sessions store mapping and report metadata only, such as file name, row count, headers, mappings, platform, and issue counts. Saved sessions do not store the full CSV/XLSX or all row values.
Image checking
Browser image checks happen locally where possible. If you choose the server image check, image URLs are sent temporarily to the backend for validation. CatalogWash does not store those URLs.
Payments, email, and logs
Payment is processed by the configured payment provider. Magic-link email is sent by the configured email provider. Basic server logs are designed to avoid row-level CSV data, full uploaded file contents, secrets, product lists, and sensitive customer data.
CatalogWash links
Export format tested with Shopify product CSV import. Not affiliated with Shopify. CatalogWash helps reduce import errors, but you should review business-critical product data before importing.