Free integrates booking callbacks with WordPress Tools → Export Personal Data and Erase Personal Data. The workflow requires native request authority and current operator review; it does not delete all booking history or certify complete anonymization.
Establish the correct subject and request
Use a verified native WordPress privacy request with the appropriate export/erase privileges. Erasure additionally requires the relevant user-deletion privilege. Viewing Hotel Booking reservations alone does not grant this authority. Direct callback calls without the matching authorized request context are rejected.
Matching preserves email local-part bytes and plus tags and folds ASCII domain case only. Changing an account email does not join all past guest bookings into one subject. Shared/reassigned or ambiguous identities require review; do not broaden the match to make a request appear complete.
Review and export
- Open the native Tools request and its current copies. Use the request ID in the Hotel Booking review controls.
- Inspect attributable booking details, ledger, notes and external/legal/audit/financial holds using existing staff permissions.
- Record current whole-subject attribution decisions. Unreviewed free text, other people/staff information, gateway metadata and signed/issued copies can be withheld with a scope report.
- Run the native export and inspect its scope and retained/manual messages. Active attributable reservations can be included; export is not erasure.
Review and erase eligible fields
Cancelled or Checked Out bookings can qualify only when obligations are resolved and the reviewed unchanged record has no holds. Active, No-show, externally owned, ambiguous and unresolved-financial cases remain retained. Unknown holds are not assumed absent.
Eligible name/email/phone fields are redacted and verified account association detached. Separately reviewed wholly attributable nullable notes/customer mail copies may be redacted. Financial/reference identities, audit, signed policy/invoice records, mixed/admin copies and external/sent mail can remain linkable. Inspect both removed and retained outcomes, even when a batch completes.
Process batches and external copies
Each scan has an upper booking-ID bound. Process pages in order; missing progress requires restarting at page one or a new native request. Newer records require another request. Replaying a committed erasure page returns its recorded outcome rather than implying retained cases were later erased. Review decisions tied to old record bytes must be inspected again when records change.
Redaction suppresses future booking mail; an in-flight transport can defer/retry the batch. It cannot recall sent mail, exports or backups. Account detachment neither deletes the WordPress user nor revokes existing bearer booking links. Handle retained/external copies separately and do not rewrite signatures or invoice files through this workflow.
No code rollback can undo erasure. Use synthetic fixtures before operational requests and follow backup/incident recovery.
