Doula plugin privacy
The intake that holds an unannounced due date and the story of the last birth
A doula booking page can look like a calendar and a contact form. The same form often asks for a due date, a planned birth location, who will be allowed in the room, the provider's name, and "tell us about your previous birth" — plus birth-plan PDF uploads — and stores those answers next to the client's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a first-trimester due date nobody has announced, next to a free-text trauma narrative about the last birth and a support-people list that names who to keep out — the contact form that knows before the grandparents do, typed once into a vendor table next to a marketing pixel. A consult request is not a confirmed pregnancy. A due-date field is a plan the client typed, not a medical record. A previous-birth narrative is the client's account, not the hospital's chart. An on-call booking block is a calendar reservation, not proof a birth occurred. A page request is not proof anyone is pregnant. The page URL can say doula even when no form is submitted. Ask what happens to the due-date answer and the previous-birth-experience field after the consult — the intake holds an unannounced due date and the story of the last birth, and the row outlives the visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a doula scope-of-practice or licensure claim, a clinical-outcomes or safety claim, a HIPAA or health-privacy coverage claim, an insurance or Medicaid reimbursement 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 prenatal bookings, birth-story notes, and page tags go
Bookings and notes on your WordPress site
Check which due-date, birth-location-plan, previous-birth-experience, support-people, or provider-name fields you enable, who can open form entries and prenatal or on-call bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the intake holds an unannounced due date and the story of the last birth. Notification emails can also copy those fields off-site. One table can list every prenatal slot next to a due date and a previous-birth narrative. Ask your web vendor not to keep previous-birth-experience next to due-date in one open submissions list longer than operations need, and to purge intake rows when the booking ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not proof a birth occurred. An uploaded birth-plan PDF is not a hospital chart.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the doula booking page. That page request can reach a vendor host before anyone submits. The page URL can say doula even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "confidential support" badge is not a verified storage path.
Prenatal / on-call booking, birth-story intake, 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 birth-support SaaS platforms 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A prenatal visit slot or an on-call window block is a booking you create; a service name such as prenatal consult, birth package, or on-call window is a label you configure. Neither is a documented default. Due-date, birth-location-plan, previous-birth-experience, support-people, or provider-name questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof a birth occurred — and a CSV export of a two-week on-call block next to a due-date answer is still a calendar of when a household expects to leave for the hospital. Emails can include those custom fields and copy the appointment off-site. 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. | Prenatal visits and on-call window blocks stored 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. Due-date, birth-location-plan, previous-birth-experience, support-people, or provider-name questions are fields you add; they are not documented defaults. Completing the form can store a due-date answer next to a birth-location-plan field, a previous-birth-experience narrative, a support-people list, a provider-name field, and optional birth-plan PDF uploads — typed once as the contact form that knows before the grandparents do into the same tables as a newsletter signup. A consult request is not a confirmed pregnancy. A due-date field is a plan the client typed, not a medical record. A previous-birth narrative is the client's account, not the hospital's chart. An on-call booking block is a calendar reservation, not proof a birth occurred — and a staff login can open "due June 12, hospital birth, keep aunt out of the room, last birth: emergency section" next to a birth-plan PDF. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Birth-story intake entries stored in WordPress; optional birth-plan PDF 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 due-date, birth-location-plan, previous-birth-experience, support-people, or provider-name field was sent. A page request from this script is not proof anyone is pregnant. The page URL can say doula even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. | 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. Due-date, birth-location-plan, previous-birth-experience, support-people, or provider-name fields often depend on the fields you configure. A consult request is not a confirmed pregnancy. A due-date field is a plan the client typed, not a medical record. A previous-birth narrative is the client's account, not the hospital's chart. An on-call booking block is a calendar reservation, not proof a birth occurred. A marketing-tag page request is not proof anyone is pregnant. The page URL can say doula even when no form is submitted. The intake that holds an unannounced due date and the story of the last birth — that is a storage path next to a previous-birth-experience field, not a feature these plugins claim. This page is about that birth-story intake, not a midwife chart, a lactation consult, a surrogacy application, an adoption home study, or an egg-donor screening. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "confidential support" 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 doula scope of practice or licensure, clinical outcomes or safety, HIPAA or health-privacy coverage status, or insurance or Medicaid reimbursement. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-doula-plugin-privacy