Med-spa and aesthetic-clinic plugin privacy
Where are med-spa bookings and before-and-after photos stored?
Med-spa and aesthetic-clinic sites can use a booking plugin for appointments and configured intake notes, a slider plugin for published before-and-after photos, or a vendor scheduling widget. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, which photos you publish, where vendor hosts handle bookings, and how long booking rows, published photos, and backups are kept.
Documentation review only. This is not legal or medical advice, or a HIPAA, GDPR, or other compliance assessment.
Scan your site for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, booking records, published photo files, staff permissions, vendor accounts, or backups.
Where booking records and treatment photos are stored
Records and published photos stored on your WordPress site
Check which booking or intake fields you enable, who can open client rows, which before-and-after photos you publish, and how long records, media files, and backups are kept. Notification emails can also copy the same answers off-site.
Bookings handled by a vendor
Some scheduling tools load a vendor widget when a visitor opens the booking page. Review account access and retention there. A browser scan cannot inspect stored booking records.
Med-spa booking, case-photo, and vendor-booking setups
No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.
Three plugins reviewed from public documentation. Specialty med-spa practice software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Booktics – Appointment Booking Calendar for Service Businesses Documented self-hosted appointment plugin marketed for salons, spas, clinics, and wellness (plugin version 1.0.29). WordPress admin screens cover services, team, customer history, contact details, and booking records. Treatment-area, consultation, or medical-note questions are documented as Pro custom booking fields, not as free-version defaults. Optional Stripe, Google Calendar, Google Meet, and FluentCRM send data only when you enable them. Retention of booking or customer rows is not specified as a default purge. Public booking-form browser hosts are unverified. | Booking records and customer history stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Twenty20 Image Before-After Documented local before-and-after slider (plugin version 2.1.0). The listing markets medical procedures and beauty transformations. Before and after images are Media Library attachments selected by ID. The listing does not document stripping camera metadata from the original upload, password-protecting a case, or blocking direct file URLs. These are published comparison photos staff choose, not a private intake photo attached to a booking. Who appears in a slider, consent to publish, and how long media files and backups are kept are not specified as defaults. Visitor-browser hosts for the public shortcode are unverified. | Published before-and-after photos stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| SimplyBook.me – Booking and reservations calendar Connects WordPress to SimplyBook.me (plugin version 3.5.0). The listing states settings, bookings, and client data are stored in the SimplyBook.me account through its API, not in the WordPress database. The public booking widget loads simplybook.me/v2/widget/widget.js. The listing says the widget sends the visitor IP when a page with the widget loads, and booking data when the visitor books. Unconnected sites load a demo widget from demowidgetwpplugin.simplybook.it. Treatment-area or consultation questions depend on the form you configure in that account. Review access and retention there. Plugin dashboard API calls and simplybook.rsp-auth.com onboarding are admin paths, not listed here as visitor-browser hosts. | Bookings handled through a SimplyBook.me vendor host | simplybook.me | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Treatment-area notes, consultation answers, or insurance details often depend on the fields you configure. Published before-and-after photos are not a private intake file. Camera metadata and unlisted media URLs are described only when a plugin documents them. Consent timing, access controls, and retention have not been tested. This page describes storage paths only. Review stored records, published photos, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-medspa-plugin-privacy