Data Processing Addendum

This document supplements and incorporates the previous data processing addendum. Existing provisions continue to apply except where this supplement provides more specific information about enabled WooCommerce assistance.

WooCommerce processing instructions and Exhibit A supplement

For customer-enabled WooCommerce assistance, relevant data subjects include store visitors, signed-in customers and guests who verify one order. Processing can include public product descriptions and options, bounded native-cart contents and context, explicit action receipts, minimized order status and shipment details, and separately enabled purchase/refund correlations. Private orders are not imported into the public knowledge index.

Guest order numbers, email addresses and verification codes are submitted directly to the customer's WordPress installation. The store sends the code through its configured mail service. Chat4U receives an expiring opaque proof, not the code, WordPress password, native login cookie or a general customer-account credential. A cart handle does not establish order ownership. Minimized authorized order results may be processed by the configured model to answer the current request; the delivered private answer is replaced with a neutral verification message in durable Chat4U history.

The customer's hosting and mail suppliers operate the native store boundary. Chat4U's configured hosting, security and AI processors operate its service boundary under the existing DPA and subprocessor information. Deletion assistance covers Chat4U copies and derived evidence; it does not imply deletion of the merchant's underlying order. If a plugin cannot be reached, physical deletion on the merchant's host requires recovery or merchant action. Necessary minimized unresolved-action evidence and mandatory legal/security records may remain for their separate purposes.