Booking plugin data paths
Where WordPress booking plugins keep or send client details
Booking forms collect names, emails, phone numbers, and appointment reasons. Some plugins keep those records on your WordPress host. Others send client or payment data to an outside service when you enable that setup. This table summarizes the documented setups below. Your settings can change where data goes.
Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.
Scan your booking pageHow we group booking plugins
We compare the booking setups named below. A plugin can keep appointment records on your server and still send client details to an outside service. Some features must be enabled in plugin settings. We have not tested when requests start relative to cookie consent or assessed how long data is kept.
Booking plugins
No paid placement. On your server first, then outside services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Receiving domains | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Booking Calendar (local bookings) WordPress.org Privacy Notices: booking details are stored in your WordPress database. Booking Calendar does not send or store those details on the vendor servers. Optional integrations you configure may send data outside. | On your server | None in the documented default path. | Not assessed | Not tested |
| |
| LatePoint (Stripe enabled) LatePoint WordPress.org listing: when Stripe is enabled, card data is handled by Stripe on the booking payment step. LatePoint does not hold the funds. The listing does not name verified receiving domains. Manual pay-later setups are outside this row. | Outside payment service | Receiving domains not verified | Not assessed | Not tested | ||
| Amelia We have not reviewed this plugin's booking data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| Bookly We have not reviewed this plugin's booking data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
| |
| Simply Schedule Appointments We have not reviewed this plugin's booking data path yet. | Not reviewed | Documentation not reviewed yet. | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named booking setups. It does not show what loads on your site. Local storage and outside processing can both apply. We have not tested consent timing, and we have not assessed how long data is kept. This scan does not read appointment records inside your database.
Documentation snapshot: Sep 28, 2026. Sources are linked in each reviewed row.
Scan your booking page/wp-booking-plugin-privacy