Privacy
Conservative data handling for a catalog operations product.
This page summarizes how ACP Feed Optimizer approaches store data, audit behavior, provider usage, and deletion requests. It is written conservatively and should be paired with your signed commercial terms.
What data ACP uses
ACP uses store and catalog data needed to run audits, issue detection, product review workflows, billing operations, and support. The exact data used depends on the workflows the merchant enables.
Read-only audit behavior
The public audit flow is designed to be read-only first. Merchants can review issues and recommendations before they enable deeper catalog workflows.
When product changes can happen
Product-level changes only happen when a merchant enables the relevant workflow and uses the review, approval, or publish controls available in the application.
AI provider handling
AI provider configuration is relevant for deeper optimization workflows, not for starting the first audit. Provider usage should be reviewed by the merchant based on the models and workflows they choose to enable.
Retention, deletion, and requests
ACP retains data needed to operate the service, support merchants, and meet legal obligations.
Merchants can request data export or deletion workflows through support.
More operational detail lives on the Security & Data Handling page and in the DPA summary.
Legal review recommended before publication of any final contractual retention windows or region-specific privacy language.