Keepsake ultrasound plugin privacy
The booking that dates the pregnancy before anyone was told
A retail imaging studio can hold the most time-sensitive secret there is: a booking form that stores weeks-along and due date for a pregnancy that may not have been announced to an employer, a family, or anyone. A gallery add-on can upload fetal images tied to the parents' names; a gender-reveal package field can record the answer before the party does. When a pregnancy is lost, the entries table can still hold the booking — a date the family never wants resurfaced by a marketing email. Weeks-along, due-date, parent-name, partner-name, fetal-image upload, gender-reveal package, phone, email, and appointment-date fields are configured, not documented defaults. A weeks-along answer is a stored select or number, not a medical determination. A due date is a stored date, not proof anyone was told. A fetal-image upload is a stored file, not a diagnostic study. A gender-reveal package field is a stored service label, not proof a party happened. A keepsake-ultrasound booking is not proof anyone received a scan. A page request is not proof anyone booked. The page URL can say keepsake ultrasound even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings, entries, and gallery albums, and how long records, fetal-image files, emails, and backups are kept.
Documentation review only. This is not legal advice, a medical diagnosis, a clinical OB-imaging claim, a HIPAA claim, a miscarriage-outcome claim, a doula claim, a midwife claim, a surrogacy claim, a cord-blood claim, a fertility 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, gallery albums, email inboxes, staff permissions, vendor accounts, or backups.
Where due dates, fetal images, and bookings go
Keepsake bookings and intake forms handled on your WordPress site
Check which weeks-along, due-date, parent-name, partner-name, gender-reveal package, phone, email, or appointment-date fields you enable, who can open form entries and bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a session that never happened or after a pregnancy that ended. Notification emails can also copy the same weeks-along answers, due dates, and parent names off-site. One table can name the parents, the due date, and a gender-reveal package next to a phone, even when no scan begins. Ask your web vendor not to collect a weeks-along answer next to a due date on the first public form, not to store those fields next to parent names in one open bookings list, and to purge unused intake rows after the session window closes. A privacy-policy page does not by itself limit who can export a booking list. A stored due date is not proof anyone was told.
Fetal-image galleries on your WordPress site
Some gallery tools store fetal-image originals under your WordPress uploads folder and can keep albums reachable by direct URL after the session. A gallery album tied to a parent name can sit after a pregnancy that ended. Review who can open albums, whether image files remain reachable without a gallery login, and how long originals are kept. A browser scan cannot inspect stored bookings or fetal-image files that never load in the visitor browser. A "private keepsake gallery" badge is not a verified storage path.
Keepsake ultrasound booking, form, and gallery 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 elective-ultrasound SaaS tools without a WordPress.org listing are 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 keepsake ultrasound session is a booking you create; a service name such as 3D/4D keepsake ultrasound, gender-reveal package, or elective imaging session is a label you configure. Neither is a documented default. The stored service name can say keepsake ultrasound or gender reveal in plain text before anyone arrives. Weeks-along, due-date, parent-name, partner-name, phone, email, or appointment-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A weeks-along answer is a stored select or number, not a medical determination. A due date is a stored date, not proof anyone was told. A gender-reveal package label is a stored service name, not proof a party happened. A booked slot is not proof anyone received a scan. Cancelling or missing the slot later does not erase the weeks-along answer, due date, or parent name already stored, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became a session, or after a pregnancy that ended, is not a documented default of the plugin. The appointments list can show who is booked this week and at which due date. 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. | Keepsake-ultrasound 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. Weeks-along, due-date, parent-name, partner-name, gender-reveal package, phone, or email questions are fields you add; they are not documented defaults. Optional fetal-image or referral uploads are files you accept; those file types are not documented defaults. A weeks-along answer is a stored select or number, not a medical determination. A due date is a stored date, not proof anyone was told. A fetal-image upload is a stored file, not a diagnostic study. A gender-reveal package field is a stored service label, not proof a party happened. A keepsake-ultrasound form is not proof anyone received a scan. 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 happened, or after a pregnancy that ended, is not a documented default of the plugin. | Keepsake intake and package-selection entries stored in WordPress; optional uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| NextGEN Gallery Documented self-hosted gallery plugin. This row covers NextGEN Gallery when it serves photos from your WordPress install. On resize it copies camera metadata from the original onto the generated file. The listing does not document stripping GPS from the original upload. A fetal-image upload tied to a parent name is a stored file path you configure, not a documented default album name. A gallery album labeled keepsake ultrasound or gender reveal is a label you create, not a documented default. A fetal-image file is a stored upload, not a diagnostic study. A reachable uploads URL is a storage path, not proof a session happened. EXIF in an uploaded original is a property of the file you accepted, not a location claim about a clinic. Social-feed galleries are not this row. Consent timing is not tested here. How long an album sits after a session that never happened, or after a pregnancy that ended, is not a documented default of the plugin. | Fetal-image galleries and deliverable albums stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Weeks-along, due-date, parent-name, partner-name, fetal-image upload, gender-reveal package, phone, email, or appointment-date fields often depend on the fields you configure. A weeks-along answer is a stored select or number, not a medical determination. A due date is a stored date, not proof anyone was told. A fetal-image upload is a stored file, not a diagnostic study. A gender-reveal package field is a stored service label, not proof a party happened. A keepsake-ultrasound booking is not proof anyone received a scan. A gallery image URL is not proof a session happened. The page URL can say keepsake ultrasound even when no form is submitted. The due date, the fetal-image gallery, and the parent name can sit after a session that never happened or after a pregnancy that ended. This page is about the booking that dates the pregnancy before anyone was told, not a doula birth intake, not a midwife prenatal history, not a surrogacy pregnancy-history résumé, not a cord-blood banking enrollment, and not a fertility conception intake. Ask your web vendor who can open entries and albums, whether fetal-image files remain reachable by direct URL, and how long records and backups are kept. A "private keepsake 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 medical diagnosis, clinical OB imaging, HIPAA, miscarriage outcomes, doula support, midwifery, surrogacy, cord-blood banking, or fertility treatment. Review stored records, gallery originals, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 17, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress forms privacy
- WordPress booking plugin privacy
- WordPress gallery plugin privacy
- All privacy guides
/wp-keepsake-ultrasound-plugin-privacy