Assisted living plugin privacy
Where does the tour request that describes a parent who doesn't know you're asking go?
An assisted-living tour-request or waitlist form can collect a parent's name and age, memory or mobility decline, incontinence, wandering incidents, medication list, and the family's budget range for care — typed by an adult child into a local-first form or tour-slot booking plugin. File fields can store physician assessments in the site uploads folder. The data subject may never be told the form exists and often has not yet agreed to move. The row can quietly outlive a tour that never became a move-in. A marketing tag on the same tour page can send a page request to a vendor host before anyone submits. A page request is not proof that a parent's condition was described. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and entries, where uploaded files land, which tags load on the tour page, and how long records, files, and backups are kept.
Documentation review only. This is not legal or medical advice, an elder-care licensing review, a Medicaid eligibility assessment, a care-outcome 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 bookings, form entries, uploaded physician assessments, email inboxes, staff permissions, vendor accounts, or backups.
Where tour bookings, waitlist answers, and page tags go
Bookings and files handled on your WordPress site
Check which parent-name, age, decline-description, medication, assessment-upload, or budget fields you enable, who can open bookings and form entries, where uploaded physician assessments live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a tour that never became a move-in. Notification emails can also copy the same answers off-site. Ask your web vendor not to collect full medication lists on the first public form, and to purge tours that never became residents.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the assisted-living tour or waitlist page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off tour pages if you do not want that page request. A browser scan cannot inspect stored form entries. A "secure client forms" badge is not a verified storage path.
Assisted-living tour, waitlist, 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 senior-living CRM 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 clinics and service bookings (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. Parent name and age, memory or mobility decline, incontinence, wandering incidents, medication list, or family budget range are custom fields you add (textarea, select, or input); they are not documented defaults. A tour booking is not an admission. Emails can include those custom fields. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge and does not guarantee tour-length retention limits. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified. | Tour-slot bookings and custom intake fields 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. Parent name and age, decline-description, medication, or budget questions are fields you add; they are not documented defaults. Physician-assessment uploads are files you accept; they are not documented defaults. A tour or waitlist entry is not an admission. An uploaded assessment is not a care plan. Entries can quietly outlive a tour that never became a move-in in plugin tables. Notification emails can copy field values off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | 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 parent's decline description or medication list was sent. A page request from this script on an assisted-living tour or waitlist page is not proof that a parent's condition was described — and a pre-consent tag on that page can still treat assisted-living shopping intent as an audience segment from the URL alone. Consent timing has not been tested. Review which tags you enable on tour and waitlist 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. Parent names and ages, decline descriptions, medications, wandering notes, physician assessments, or budget ranges often depend on the fields you configure. A tour request is not an admission. An uploaded assessment is not a care plan. A marketing-tag page request is not proof that a parent's condition was described. Ask your web vendor who can open bookings and entries, where uploaded files live, whether a marketing tag loads on the tour page, and how long records and backups are kept. A "secure" or "client forms" 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 elder-care licensing, Medicaid eligibility, or care outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on tour pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress file upload plugin privacy
- WordPress hospice plugin privacy
- WordPress home care plugin privacy
- All privacy guides
/wp-assisted-living-plugin-privacy