Free maintains separate Contact and Newsletter lifecycle records. Their cleanup settings do not purge reservations, payment ledgers or historical Pro data, and local deletion cannot recall data already exported or sent externally.
Assign the right staff permissions
Use the Contact and Newsletter management screens for everyday operations. Communication settings and subscriber CSV export are separate privileges and are administrator-only by default. Hotel Manager can manage messages/subscribers but does not receive those two privileges automatically; Receptionist does not receive communication privileges by default.
A subscriber CSV contains personal data. Limit its filters/scope, keep it private and include downloaded copies in the operator’s retention procedure. Subscriber management does not start marketing campaigns automatically.
Configure cleanup deliberately
Open Hotel Booking → Newsletter & Contact and review the current retention settings and preview before saving shorter periods.
| Record group | Default age | Basis/behavior |
|---|---|---|
| Pending newsletter | 30 days | First request age; resend does not reset it |
| Unsubscribed newsletter | 365 days | Unsubscribed lifecycle age |
| Contact messages | 365 days | Message lifecycle cutoff |
| Contact spam | 30 days | Spam cutoff |
| Subscribed newsletter | No automatic expiry in this policy | Remains until an applicable explicit action |
Saved values range from 1 to 3,650 days. Shortening a period can make existing rows eligible; review the displayed impact and confirmation before saving. Cleanup runs in bounded scheduled batches, not an exact-minute deletion guarantee. WordPress cron depends on execution/traffic; configure an appropriate system scheduler when operational timing requires it.
Use native privacy tools
WordPress Tools → Export/Erase Personal Data includes separate Contact and Newsletter callbacks. Inspect the specific component’s result and completion state. Removing a local subscriber removes associated local lifecycle/token records through that workflow; deleting a Contact message does not delete an email already received by hotel staff.
Do not apply booking eligibility rules mechanically to these communication tables, or assume communication erasure covers booking records for the same address. Booking export/erase has its own authority, attribution and hold review.
Mail, uninstall and recovery
Check notification state and supported resend/test-mail actions independently from stored intake. Accepted transport is not inbox delivery. Do not turn a failed notification into another enquiry automatically.
Default uninstall preserves data. The optional purge-on-uninstall setting affects communication data/settings only, not a booking/financial purge. Destructive cleanup or erasure is not reversed by reinstalling code. Protect retained backups and external copies separately; never use uninstall as an update or recovery method.
