Black Friday
Skip to documentation content

Security & Privacy

Understand booking data and retention

Free stores reservation identities, stay details, financial snapshots, status and correspondence. Pro can add further historical copies. Keeping a booking, redacting selected identifiers and deleting every linkable copy are different outcomes.

Free stores reservation identities, stay details, financial snapshots, status and correspondence. Pro can add further historical copies. Keeping a booking, redacting selected identifiers and deleting every linkable copy are different outcomes.

Inventory the data before acting

Review direct guest name/email/phone, account association, room/service/tax/coupon snapshots, settled payments/refunds, transactions and activity. Also consider queued/sent mail, Room Policy acknowledgements, cancellation decisions, issued invoices, external gateways/OTA systems, exports and backups.

The core booking privacy workflow is available without Pro. It can encounter historical Pro-owned copies without enabling a paid feature; missing or unresolved history can remain manual/incomplete.

Retention is an operator decision

Core does not provide a scheduled booking purge or a numeric booking-retention period. Define the hotel’s handling procedure and obligations separately. Contact/Newsletter retention controls apply to their own communication records, not reservations or financial ledgers.

Booking situation Erasure treatment
Eligible Cancelled or Checked Out; reviewed attribution and resolved obligations/no holds Selected direct identifiers may be redacted
Active or No-show reservation Retained for operational review
Unresolved payment/refund, unknown holds or identity ambiguity Retained/manual
External inventory block or external reservation reconciliation Retained/manual under its ownership
Signed/issued/audit/reference copies Can remain linkable; no promise of complete anonymization

An Unpaid/Paid label alone does not establish that financial obligations are resolved. The actual ledger and related records are checked. A stale per-record review must be inspected again.

Understand a successful partial redaction

Eligible direct fields become Redacted guest, a redaction-placeholder email and a null phone; a verified account association is detached. Reviewed wholly attributable nullable notes/customer mail copies may also be redacted. Mixed/staff text, signed records, financial identities and external copies can remain.

The WordPress user is not deleted by account detachment, and existing bearer confirmation links are not revoked by that action. Future booking mail is suppressed after redaction; an already in-flight or delivered message cannot be recalled.

Recovery boundary

Code rollback and plugin reactivation do not restore erased personal information. Restoring an old database over new bookings or privacy outcomes can reintroduce erased data and lose newer transactions. Plan restore and reconciliation deliberately rather than using backup restoration as an automatic undo.

Use native export and erase procedures and inspect retained/manual results for every request.

Was this article helpful?

Your feedback helps us improve the documentation.