Know where the data lives
Contacts, consent, preferences, drafts, queue records and reporting data are stored in your WordPress database. The vendor does not receive your subscriber list as plugin telemetry. Your chosen transport receives the data needed to send; enabled SendGrid feedback receives signed provider events locally.
An optional Pro update connection shares its token, site fingerprint and installed versions with the configured publisher. This is separate from subscribers and ordinary local Pro features.
Export before changing the installation
Use Audience to export contacts and save authored designs or portable kits separately. Protect these exports because contact files contain personal information. WordPress privacy export and erasure cover supported newsletter records and preferences.
Erasure removes or cancels matching unfinished private CSV work while preserving unrelated jobs. A keyed suppression marker remains to prevent accidental reimport; it is not a re-created subscriber profile.
Pause and check uninstall behavior
Pause sending before deactivation or removal. In Settings, inspect Retention and ownership. Complete deletion is an explicit separate choice; default removal retains data. Never uninstall as an update strategy.
Private CSV jobs expire after 24 hours and are removed by scheduled cleanup; completed or cancelled work clears raw CSV immediately. Operational event retention is configurable. Sent, cancelled and skipped queue rows and their attempt receipts become eligible for scheduled removal after 90 days; unresolved attempts remain for review. Provider correlations and feedback receipts also have 90-day scheduled retention. Suppression fingerprints remain until explicit plugin-data deletion. Reporting uses its separate configured retention period.
Distinguish Free from Pro removal
Removing Pro by default retains authored content and saved data. Common saved campaign blocks remain editable in Free; dependent Pro workflows, audience rules and required-review sends are held. Full deletion deliberately removes the relevant plugin data and protection history.
Historical WooCommerce coupons remain merchant records. Preserve database and signing options for existing public links and review any separate provider-side activity. A file export is not a substitute for a consistent full backup.