Makeup artist plugin privacy
The bridal trial that logs your face, your venue, and the morning the house stands empty
A bridal or event makeup booking can ask for the event date, the venue, the getting-ready address, the trial date, the size of the party, skin sensitivities and allergies, and inspiration photo uploads of the client's own face. A form built to schedule a glam morning can hold a published itinerary of the exact hours a named home stands empty, face photos, and a minor medical note, all in a form plugin entries table. Event-date, venue, getting-ready-address, trial-date, party-size, skin-sensitivity, allergy, and face-photo fields are configured, not documented defaults. Optional face photos go in the site uploads folder. A booking is not proof makeup was applied. A getting-ready address is a stored location, not proof the house is empty. A face photo is an upload, not a likeness that exists. An allergy answer is a stored note, not a medical record. An event date is a stored date, not proof anyone attended. A page request is not proof anyone booked. The page URL can say makeup artist even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and trial pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a medical claim, a HIPAA claim, an allergy claim, an occupancy claim, a likeness claim, a wedding claim, or a 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where trial bookings, face photos, and page tags go
Trial bookings and forms handled on your WordPress site
Check which event-date, venue, getting-ready-address, trial-date, party-size, skin-sensitivity, allergy, or face-photo fields you enable, who can open form entries and bookings, where uploaded face photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a trial that never became an event. Notification emails can also copy the same getting-ready addresses, allergy notes, and face photos off-site. One table can name the house, the morning it stands empty, and a photo of the client's face next to a name, even when the event never happens. Ask your web vendor not to collect a getting-ready address next to an event date and a face photo on the first public form, not to store that empty-house itinerary next to a name in one open submissions list, and to purge unused trials after the date passes. A privacy-policy page does not by itself limit who can export a booking list or republish an upload. A stored booking is not proof makeup was applied.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the makeup-artist booking or trial page. That page request can reach a vendor host before anyone submits. The page URL can say makeup artist even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and trial pages if you do not want that page request. A browser scan cannot inspect stored getting-ready addresses, allergy notes, or face photos. A "bridal glam" badge is not a verified storage path.
Makeup-artist booking, trial, and marketing-tag 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 salon or POS 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 |
|---|---|---|---|---|---|---|
| Easy Appointments Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A bridal trial is a booking you create; a service name such as bridal trial, event makeup, or getting-ready is a label you configure. Neither is a documented default. Event-date, venue, getting-ready-address, trial-date, party-size, skin-sensitivity, allergy, or face-photo questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked trial is not proof makeup was applied, and is not proof the house is empty. Cancelling or missing the slot later does not erase the getting-ready address, allergy note, or face photo already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a trial that never became an event is not a documented default of the plugin. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified. | Trial bookings, custom intake fields, and automatic confirmation emails on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Forminator Forms – Contact Form, Payment Form & Custom Form Builder Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Event-date, venue, getting-ready-address, trial-date, party-size, skin-sensitivity, allergy, or face-photo questions are fields you add; they are not documented defaults. A face or inspiration photo is a file you accept; that file type is not a documented default. A booking is not proof makeup was applied. A getting-ready address is a stored location, not proof the house is empty. A face photo is an upload, not a likeness that exists. An allergy answer is a stored note, not a medical record. An event date is a stored date, not proof anyone attended. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. How long a trial sits after it never became an event is not a documented default of the plugin. | Trial and face-photo entries stored in WordPress; file uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| PixelYourSite – Your smart PIXEL (TAG) & API Manager Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that a getting-ready-address, allergy, or face-photo field was sent. A page request from this script is not proof anyone booked. The page URL can say makeup artist even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and trial pages. Keep marketing tags off those pages if you do not want that page request. A tagged trial page can re-confirm makeup-artist interest next to a stored address and files; this row does not claim an event from that request. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Event-date, venue, getting-ready-address, trial-date, party-size, skin-sensitivity, allergy, or face-photo fields often depend on the fields you configure. A booking is not proof makeup was applied. A getting-ready address is a stored location, not proof the house is empty. A face photo is an upload, not a likeness that exists. An allergy answer is a stored note, not a medical record. An event date is a stored date, not proof anyone attended. A marketing-tag page request is not proof anyone booked. The page URL can say makeup artist even when no form is submitted. The getting-ready address, the face photo, and the allergy note can sit after the trial never becomes an event. This page is about a bridal trial that logs a face, a venue, and the morning the house stands empty, not a salon chair-side beauty record, not a tattoo design upload, not a drone-photography event aerial, and not an RSVP guest list. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or trial page, and how long records and backups are kept. A portfolio badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess medical status, HIPAA, allergy, occupancy, likeness, or wedding claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and trial pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress gallery plugin privacy
- All privacy guides
/wp-makeup-artist-plugin-privacy