Vertex SEO Data Use Schedule

The App uses merchant identity and membership to verify entry to the bound store; store, installation, and generation data; encrypted server-side provider tokens; product, catalog, SEO-field, image, and link data; drafts, recommendations, and apply or rollback evidence; and webhook, security, support, and entitlement records.

The certified SEO path does not process payment cards, passwords, order content, customer addresses, phone numbers, or messages. The App does not grant commercial entitlement locally and does not automatically publish an SEO change; merchant review and explicit apply are required.

Today the App receives authorized store and catalog data, signed events, and subscription observation from Zid. It sends a metadata change to Zid only after merchant review. The current Salla path is limited to authorization, lifecycle, and subscription-observation data and cannot reach the SEO catalog or metadata mutation without central commercial entitlement. The App sends limited product context to Vertex's governed AI runtime when a recommendation is requested. There is no publicly enabled Search Console flow.

Projections, results, and evidence are stored in approved Vertex services. Uninstall stops authority and future work; it is not deletion. This Schedule does not promise a numeric deletion period while deletion and time-based retention are not implemented for every record class; it will be updated before enabling a new data category, processor, region, or capability.