Babyproofing plugin privacy
The hazard walkthrough that inventories your home's dangers and dates the baby
A babyproofing consult can look like outlet covers and a gate. It is also a hazard walkthrough: stairs, pool gate, blind cords, the cabinet where the cleaners live — and the first intake question dates the baby (due date or crawl stage). The report pairs a stranger's annotated map of your house's dangers with the age of the child living in it. The consult row can announce a newborn at an address before any public record does, and the hazard list reads as an access brief. Due-date, crawl-stage, stairs-note, pool-gate, blind-cords, and cabinet-hazard fields are configured, not documented defaults. Optional room photos of hazards go in the site uploads folder. A consult booking is not proof a walkthrough happened. A due-date answer is a stored note, not proof a newborn lives there. A page request is not proof anyone booked a consult. The page URL can say babyproofing 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 account pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a child-endangerment claim, a custody claim, an abuse-reporting 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 consult bookings, hazard intakes, and page tags go
Consult bookings and hazard forms handled on your WordPress site
Check which due-date, crawl-stage, stairs-note, pool-gate, blind-cords, or cabinet-hazard fields you enable, who can open form entries and bookings, where uploaded hazard photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a walkthrough. Notification emails can also copy the same baby age and hazard list off-site. One table can name the house, the due date or crawl stage, and the hazard map next to a name, even when the consultant never comes. Ask your web vendor not to collect a due date next to a hazard map on the first public form, not to store pool-gate notes next to baby age in one open submissions list, and to purge unused consult bookings after the date passes. A privacy-policy page does not by itself limit who can export a customer list. A stored booking is not proof a walkthrough happened.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the babyproofing booking or account page. That page request can reach a vendor host before anyone submits. The page URL can say babyproofing even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and account pages if you do not want that page request. A browser scan cannot inspect stored due dates, crawl stages, or hazard maps. A "new parent" badge is not a verified storage path.
Babyproofing booking, hazard-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 child-safety or inspection 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 babyproofing consult is a booking you create; a service name such as prenatal walkthrough, crawl-stage visit, or follow-up install is a label you configure. Neither is a documented default. Due-date, crawl-stage, stairs-note, pool-gate, blind-cords, or cabinet-hazard questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked consult is not proof a walkthrough happened, and a due-date answer is not proof a newborn lives there. Cancelling or missing the slot later does not erase the hazard list, baby age, or due date already stored next to an address, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a walkthrough 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. | Consult 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. Due-date, crawl-stage, stairs-note, pool-gate, blind-cords, or cabinet-hazard questions are fields you add; they are not documented defaults. A room photo of a hazard is a file you accept; that file type is not a documented default. A consult request is not proof a walkthrough happened. A due-date answer is a stored note, not proof a newborn lives there. A hazard list is a stored map, not a verified inspection. 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 an account row sits after a request that never became a walkthrough is not a documented default of the plugin. | Account and hazard-intake form 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 due-date, crawl-stage, stairs-note, or pool-gate field was sent. A page request from this script is not proof anyone booked a consult. The page URL can say babyproofing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and account pages. Keep marketing tags off those pages if you do not want that page request. A tagged babyproofing page can re-confirm consult interest next to a stored address and baby age; this row does not claim a walkthrough 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. Due-date, crawl-stage, stairs-note, pool-gate, blind-cords, or cabinet-hazard fields often depend on the fields you configure. A consult booking is not proof a walkthrough happened. A due-date answer is a stored note, not proof a newborn lives there. A marketing-tag page request is not proof anyone booked a consult. The page URL can say babyproofing even when no form is submitted. The hazard list and the baby age can sit after the consultant never comes. This page is about a hazard walkthrough that dates the baby, not a home-inspection buyer defect list, not a music-lesson stranger at the door, and not a house-cleaning weekly briefing. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or account page, and how long records and backups are kept. A "new parent" 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 child-endangerment claims, custody status, or abuse reporting. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and account pages, and backups.
Documentation snapshot: Oct 15, 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-babyproofing-plugin-privacy