Medical alert plugin privacy

The signup whose customer list is a list of people who live alone

A medical-alert signup can look like a pendant order. It is also a list of people who live alone, with doors, sorted by frailty. Lives-alone, fall-history, medication, mobility, key-holder, and address fields are configured, not documented defaults. Optional physician-order uploads go in the site uploads folder. Often the adult child fills the form; the wearer never typed a word. The form records isolation in a vendor table, next to who can let EMS in, next to a marketing pixel. Cancelling the install later does not unsend the confirmation email or erase the fall-history field. A signup request is not a monitoring contract. A fall-history answer is the family's account, not a medical record. A key-holder contact is a stored door-access instruction, not a consent from the key-holder. A page request is not proof anyone wears a button. The page URL can say medical-alert 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 signup pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a medical-device-regulation claim, an elder-abuse-law claim, an EMS-response-time claim, a monitoring-service-quality claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

The 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 lives-alone answers, install bookings, and page tags go

Install bookings and signups handled on your WordPress site

Check which lives-alone, fall-history, medication, mobility, key-holder, or address fields you enable, who can open form entries and bookings, where uploaded physician orders 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 monitoring contract. Notification emails can also copy the same fall history and key-holder off-site. One table can name a wearer who never filled out the form next to a door-access instruction, even when the install never happens. Ask your web vendor not to collect a lives-alone status or key-holder on the first public form, not to store that answer next to a name in one open submissions list, and to purge unused bookings after the date passes. A privacy-policy page does not by itself limit who can export a signup list. A stored booking is not proof an install occurred.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the medical-alert booking or signup page. That page request can reach a vendor host before anyone submits. The page URL can say medical-alert even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and signup pages if you do not want that page request. A browser scan cannot inspect stored lives-alone answers or key-holder names. A "confidential signup" badge is not a verified storage path.

Medical-alert booking, signup, 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 monitoring-platform software without a WordPress.org listing is outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 medical-alert install is a booking you create; a service name such as medical-alert install, in-home consult, or pendant setup is a label you configure. Neither is a documented default. Lives-alone, fall-history, medication, mobility, key-holder, or address questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked install is not a monitoring contract, and is not a medical finding about anyone named in the intake. Cancelling or missing the install later does not erase the lives-alone answer, fall history, or key-holder 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 monitoring contract 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.

Installation bookings, custom intake fields, and automatic confirmation emails on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
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. Lives-alone, fall-history, medication, mobility, key-holder, or address questions are fields you add; they are not documented defaults. A physician order is a file you accept; that file type is not a documented default. A signup request is not a monitoring contract. A fall-history answer is the family's account, not a medical record. A key-holder contact is a stored door-access instruction, not a consent from the key-holder. The wearer named in the row may never have touched the form. An uploaded physician order is a client document, not a chart entry. 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 signup sits after a request that never became a monitoring contract is not a documented default of the plugin.

Signup and document-upload entries stored in WordPress; file uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 lives-alone, fall-history, medication, mobility, or key-holder field was sent. A page request from this script is not proof anyone wears a button. The page URL can say medical-alert even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and signup pages. Keep marketing tags off those pages if you do not want that page request. A tagged signup page can re-confirm frailty interest next to a stored address and key-holder; this row does not claim a monitoring contract from that request.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Lives-alone, fall-history, medication, mobility, key-holder, or address fields often depend on the fields you configure. A signup request is not a monitoring contract. A fall-history answer is the family's account, not a medical record. A key-holder contact is a stored door-access instruction, not a consent from the key-holder. A marketing-tag page request is not proof anyone wears a button. The page URL can say medical-alert even when no form is submitted. The wearer named in the row may never have touched the form. The lives-alone answer and the key-holder can sit after the install is cancelled. This page is about a signup whose customer list is a list of people who live alone, not an alarm-company quote, a home-care intake, a hospice referral, a pet-sitting calendar, or a dialysis-clinic schedule. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or signup page, and how long records and backups are kept. A "confidential" 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-device regulation, elder-abuse law, EMS response times, or monitoring-service quality. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and signup pages, and backups.

Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-medical-alert-plugin-privacy