Boudoir photography plugin privacy

The proofing gallery that keeps the photos that were only ever meant for one person

A boudoir studio can take a pre-shoot questionnaire and a booking, then keep the session originals in the site uploads folder after the client already downloaded the album. The form can store a client name, body-image notes, scars-and-surgeries fields, who the album is a gift for, and a session date next to those files. The gift-for name is a third party who may never visit the site. A session date in an appointments list can sit next to an anniversary or deployment label. Client-name, body-image-note, scars-and-surgeries, gift-for, session-date, anniversary, deployment, and proofing-photo fields are configured, not documented defaults. Optional proofing photos go in the site uploads folder. A body-image note is a stored note, not a diagnosis. A scars-and-surgeries field is a stored note, not a medical record. A gift-for name is a stored third-party name, not proof that person received the album. A session date is a stored booking, not proof a shoot happened. An anniversary or deployment label is a stored service name, not proof of marriage or military service. An uploaded photo is a file, not proof of nudity or of a session. A proofing URL is a stored path, not proof anyone viewed the gallery. EXIF in an uploaded original is a property of the file you accepted, not a location claim. A page request is not proof anyone booked. The page URL can say boudoir photography even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries, bookings, and uploads, which tags load on booking and proofing pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a nudity claim, a medical claim, a HIPAA claim, a diagnosis claim, a marriage claim, a military-service claim, a portrait-studio claim, an aerial-archive claim, a fitting-room claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The 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 boudoir bookings, proofing photos, and page tags go

Boudoir bookings and forms handled on your WordPress site

Check which client-name, body-image-note, scars-and-surgeries, gift-for, session-date, anniversary, deployment, or proofing-photo fields you enable, who can open form entries and bookings, where uploaded originals live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a session that never became a delivered album. Notification emails can also copy the same client names, body-image notes, gift-for names, and proofing photos off-site. One table can name the client, describe the body, name the gift recipient, and attach session originals next to a date, even when the album was already downloaded. Ask your web vendor not to collect a scars-and-surgeries note next to a client name and a proofing photo on the first public form, not to store that pairing next to a gift-for name in one open submissions list, and to purge unused sessions after the album is delivered. 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 a shoot happened.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the boudoir booking or proofing page. That page request can reach a vendor host before anyone submits. The page URL can say boudoir photography even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and proofing pages if you do not want that page request. A browser scan cannot inspect stored body-image notes, gift-for names, or proofing photos. A "private client gallery" badge is not a verified storage path.

Boudoir-photography booking, proofing, 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 studio proofing or client-gallery SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 boudoir session is a booking you create; a service name such as boudoir, anniversary gift, or deployment send-off is a label you configure. Neither is a documented default. The stored service name can say boudoir in plain text before anyone sits for a camera. Client-name, body-image-note, scars-and-surgeries, gift-for, session-date, anniversary, or deployment questions are custom fields you add (textarea, select, or input); they are not documented defaults. A body-image note is a stored note, not a diagnosis. A scars-and-surgeries field is a stored note, not a medical record. A gift-for name is a stored third-party name, not proof that person received the album. A session date is a stored booking, not proof a shoot happened. An anniversary or deployment label is a stored service name, not proof of marriage or military service. Cancelling or missing the slot later does not erase the body-image notes, gift-for name, or client name already stored next to a session date, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became a delivered album is not a documented default of the plugin. The appointments list can show who is booked this week and which gift-for names repeat. 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.

Boudoir bookings, custom intake fields, and automatic confirmation emails on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
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. Client-name, body-image-note, scars-and-surgeries, gift-for, session-date, anniversary, or deployment questions are fields you add; they are not documented defaults. Proofing photos and inspiration images are files you accept; those file types are not documented defaults. A body-image note is a stored note, not a diagnosis. A scars-and-surgeries field is a stored note, not a medical record. A gift-for name is a stored third-party name, not proof that person received the album. A session date is a stored booking, not proof a shoot happened. An uploaded photo is a file, not proof of nudity or of a session. A proofing URL is a stored path, not proof anyone viewed the gallery. EXIF in an uploaded original is a property of the file you accepted, not a location claim. An original can sit in the uploads folder after the client downloaded their album. 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 pairing sits after a session that never became a delivered album is not a documented default of the plugin.

Boudoir questionnaire entries stored in WordPress; proofing-photo uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 body-image-note, scars-and-surgeries, gift-for, or client-name field was sent. A page request from this script on a boudoir booking or proofing page is not proof anyone booked, and a pre-consent tag on that page can still treat boudoir-photography interest as an audience segment from the URL alone. The page URL can say boudoir photography even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and proofing pages. Keep marketing tags off those pages if you do not want that page request. A tagged booking page can re-confirm boudoir-photography interest next to a stored client name; this row does not claim a session from that request.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Client-name, body-image-note, scars-and-surgeries, gift-for, session-date, anniversary, deployment, or proofing-photo fields often depend on the fields you configure. A body-image note is a stored note, not a diagnosis. A scars-and-surgeries field is a stored note, not a medical record. A gift-for name is a stored third-party name, not proof that person received the album. A session date is a stored booking, not proof a shoot happened. An anniversary or deployment label is a stored service name, not proof of marriage or military service. An uploaded photo is a file, not proof of nudity or of a session. A proofing URL is a stored path, not proof anyone viewed the gallery. EXIF in an uploaded original is a property of the file you accepted, not a location claim. A marketing-tag page request is not proof anyone booked. The page URL can say boudoir photography even when no form is submitted. The session originals, the body-image notes, and the gift-for name can sit after the album was already downloaded. This page is about a proofing gallery that keeps photos that were only ever meant for one person, not a wedding-or-event proofing gallery, not an aerial archive, not a mastectomy-boutique fitting, and not a wig-salon intake. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or proofing page, and how long records and backups are kept. A "private client gallery" 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 nudity, medical status, HIPAA, diagnosis, marriage, military-service, portrait-studio, aerial-archive, or fitting-room claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and proofing pages, and backups.

Documentation snapshot: Oct 16, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-boudoir-photography-plugin-privacy