WordPress Consent for Appointment Booking Plugins

A salon owner installs a booking plugin on a Friday, connects a calendar, and by Monday the site takes appointments while she works. It is a genuinely good outcome. It is also the moment three new third parties started receiving her clients' data, and nobody involved noticed.

Booking tools are installed for the diary. They should be audited for the data flows that came with the diary.

Inventory the embed like an auditor, not an installer

Load the booking page in a clean browser and record third party calls in the usual three states: before a consent choice, after rejecting, after accepting. Booking embeds commonly contact map providers for the location view, font and script hosts, the plugin vendor's own analytics, and a payment provider if deposits are taken.

If any of those set non essential cookies in the reject state, your banner is decoration on that page. Either configure the plugin to respect consent, choose the plugin's privacy or embedded mode if it offers one, or replace the map with a static image and a link, which for a single location business loses nothing a client will miss.

Collect less on the form itself

Booking forms grow fields the way desks grow paper. Name and a contact method are needed. Reason for the appointment may be needed, in broad terms. Date of birth, detailed health history, or a free text box inviting clients to explain everything are rarely needed at booking time, and a clinic or therapist should be especially careful about what lands in a plugin database before any professional relationship exists.

Every field should survive the question: what breaks if this is asked later, by a person, in the appointment itself. Most fields fail that test, and the ones that fail it are pure exposure with no operational benefit.

Reminders and follow ups are separate permissions

A text or email reminder about the appointment itself is part of the service the client booked. A marketing message next month about an offer is not, and it needs its own consent, unticked, at a moment that is not buried inside the booking flow's terms.

Booking platforms bundle these settings. Read them. The default that adds every client to a marketing list is a default chosen for the platform's growth, not for your compliance, and it will be your name on the complaint when it arrives.

Retention for diaries and old records

Booking records accumulate names, numbers, attendance patterns, and no show history indefinitely if nobody sets a limit. Decide a period tied to a real purpose: tax and accounting needs, a reasonable window for disputes, then delete or anonymise the rest.

Export and backup habits matter here too. A weekly full site backup quietly preserves booking data long after the live plugin is cleaned. Retention that ignores backups is a policy about a database, not about the data.

Frequently asked questions

What third parties does a booking plugin usually load?

Commonly map providers, the plugin vendor's own services and analytics, font or script hosts, reminder messaging services, and a payment provider if deposits are taken. Audit the booking page in a clean browser to get your actual list rather than assuming.

Can a booking form ask about health details?

Ask for the minimum needed to take the booking. Detailed health information usually belongs in the professional consultation, not a plugin form. Collecting it early creates special category data in a third party system with no benefit to the client.

Are appointment reminders marketing?

Reminders about the booked appointment are service messages tied to the booking. Offers and newsletters sent later are marketing and need their own clear consent. Check platform settings, because some bundle marketing opt in into the booking flow by default.

How long should booking records be kept?

For a defined period tied to accounting, dispute, or care related purposes, then delete or anonymise. Indefinite retention in the plugin and in site backups is the default outcome if nobody chooses a period, not a considered policy.