Local storage
Cart, identity, activity, and attribution records live in the WordPress database.
Cart Rebound does not send cart data or product telemetry to the author.
Cart, identity, activity, and attribution records live in the WordPress database.
Guest tracking is off by default and can be enabled when it fits your notice and consent model.
Choose how long unrecovered and converted records remain available.
WordPress export and erasure integrations help respond to data-subject requests.
Local storage can reduce unnecessary data sharing, but it does not decide whether a message is lawful. Document your purpose, tell shoppers what happens, collect only what you need, choose a retention period, protect admin access, and honor applicable access or deletion requests.
Your host, analytics, SMTP provider, and other plugins may process data independently. Review the privacy-conscious recovery guide and publish a store-specific privacy notice.
Storage location, guest capture, and privacy responsibility are related but not interchangeable.
Cart and recovery records stay in your WordPress database. The plugin does not send cart data or telemetry to the author. Your hosting, email provider, and other installed services may have their own data practices.
Yes, when guest tracking is enabled. The plugin can capture contact details entered during checkout. Store owners remain responsible for consent, privacy notices, and a lawful basis for recovery messages.
No plugin can make that promise. Cart Rebound provides retention controls and WordPress privacy export and erasure integrations, while the store owner remains responsible for consent, notices, retention choices, and local law.
Start with guest tracking disabled, document your choices, then test on staging.