Foster care plugin privacy
The home-study intake that inventories your household, with a child's placement row beside it
A foster-agency booking page can look like a calendar and a short application. The same form often asks who lives in the home, how many bedrooms you have, income, marriage history, a background-check acknowledgment, and a reason-for-fostering essay — and stores those answers next to the applicant's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold every household member next to an income band and a floor-plan PDF — the home-study intake that inventories your household, typed once into a vendor table next to a marketing pixel. Every person listed — including children already in the home — is a third party who never touched the form. Quieter still is a placement-inquiry or respite booking that names a child or sibling group in state custody on a private agency site. An application is not a license and not an approval. A background-check checkbox is the applicant's acknowledgment, not an agency record. A respite booking is a calendar date, not an incident report. A child named in a placement-inquiry field has no say in the row. An uploaded reference letter is a client document, not a case file. A page request is not proof anyone fostered. The page URL can say foster care even when no form is submitted. Ask what happens to the household list and the placement note after the visit — the intake inventories the house, and the row outlives the home study. 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 foster-care licensing claim, a child-welfare or CPS-procedure claim, a background-check-law claim, a placement or reunification-outcomes claim, an agency-quality 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 home-study bookings, household notes, and page tags go
Bookings and notes on your WordPress site
Check which household-members, bedrooms, income, background-check-acknowledgment, marriage-history, or reason-for-fostering fields you enable, who can open form entries and home-study or respite bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the home-study intake that inventories your household sits beside a child's placement row. Notification emails can also copy those fields off-site. One table can list every home-study slot next to a household roster and a quieter respite date. Ask your web vendor not to keep a ward's name next to an applicant's income 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 a license. Household members named in the list never touched the form.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the foster care booking page. That page request can reach a vendor host before anyone submits. The page URL can say foster care 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 "foster care" badge is not a verified storage path.
Home-study and respite booking, household 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 foster-care case-management 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 home-study visit, an orientation session, or a respite-care weekend is a booking you create; a service name such as home study, orientation, or respite is a label you configure. Neither is a documented default. Household-members, bedrooms, income, background-check-acknowledgment, marriage-history, or reason-for-fostering fields are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a license — and a CSV export of a respite slot next to a child or sibling-group note is still a calendar that turns a placement into a row. 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. | Home-study, orientation, and respite bookings 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. Household-members, bedrooms, income, background-check-acknowledgment, marriage-history, or reason-for-fostering fields are fields you add; they are not documented defaults. Completing the form can store a household-members list next to bedrooms, income, a background-check acknowledgment, marriage history, a reason-for-fostering essay, and optional reference-letter or floor-plan uploads — typed once as the home-study intake that inventories your household into the same tables as a newsletter signup. An application is not a license and not an approval. A household list names third parties who never touched the form. A background-check checkbox is the applicant's acknowledgment, not an agency record. A child named in a placement-inquiry field is a ward of the state recorded on a private site, with no say in the row. An uploaded reference letter is a client document in a site uploads folder, not a case file — and a staff login can open "spouse, two teens, three bedrooms, income band, prior divorce, why we want to foster" next to a floor-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. | Foster-care intake entries stored in WordPress; optional reference-letter and floor-plan 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 household-members, bedrooms, income, background-check-acknowledgment, marriage-history, or reason-for-fostering field was sent. A page request from this script is not proof anyone fostered. The page URL can say foster care 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. Household-members, bedrooms, income, background-check-acknowledgment, marriage-history, or reason-for-fostering fields often depend on the fields you configure. An application is not a license and not an approval. A household list names third parties who never touched the form. A background-check checkbox is the applicant's acknowledgment, not an agency record. A respite booking is a calendar date, not an incident report. A child named in a placement-inquiry field is a ward of the state recorded on a private site, with no say in the row. An uploaded reference letter is a client document in a site uploads folder, not a case file. A marketing-tag page request is not proof anyone fostered. The page URL can say foster care even when no form is submitted. The home-study intake that inventories your household, with a child's placement row beside it — that is a storage path next to a roster column, not a feature these plugins claim. This page is about that household and placement intake, not an adoption agency, a daycare roster, a home-care visit form, or a food-pantry means test. 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 "foster care" 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 foster-care licensing law, child-welfare or CPS procedure, background-check law, placement or reunification outcomes, or agency quality. 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-foster-care-plugin-privacy