Reverse mortgage plugin privacy

Where does the application your kids filled out about you go?

An adult child often types a parent's age, home value, remaining equity, health-driven urgency, and contact details into a reverse-mortgage lead form the homeowner never touches — consent-by-proxy. That row records a homeowner running out of money, written by someone else's hands, then sits in a local-first booking or form plugin behind one admin login. Lead-gen in this vertical is aggressively resold, so one submission can become a dozen cold calls while the subject knows the least about the row existing. Second subjects travel with it: heirs whose inheritance the answers price, a spouse on the deed. A marketing tag on the same lead page can send a page request to a vendor host before anyone submits — and that page request alone can treat reverse-mortgage-seeking intent as an audience segment from the URL. A page request is not proof anyone is out of money. An eligibility inquiry is not a loan application of record. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which tags load on the lead page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a lending-law claim, a HECM-regulation claim, financial advice, an elder-abuse-reporting 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 lead answers, visitor fields, and page tags go

Entries and bookings handled on your WordPress site

Check which name, phone, homeowner age, home-value, remaining-equity, or urgency fields you enable, who can open form entries and eligibility-callback bookings, where uploaded files live in the uploads folder, which inboxes and lead buyers receive copies, and how long records, files, and backups are kept after an inquiry that was completed, abandoned, or never returned. Notification emails can also copy the same homeowner identity and equity answers off-site — including when an adult child filled the form. Ask your web vendor not to store a parent's equity and urgency next to a child's contact number in one open submissions list when a short inquiry ID would do.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the reverse-mortgage lead 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 eligibility and callback pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "confidential consultation" badge is not a verified storage path.

Reverse-mortgage eligibility, callback, 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. Loan-origination and CRM platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A reverse-mortgage callback is a booking you create; a service name such as eligibility review or senior-equity consult is a label you configure. Neither is a documented default. Name, phone, homeowner age, home-value, remaining-equity, or health-driven urgency questions are custom fields you add (textarea, select, or input); they are not documented defaults. An eligibility booking is not a loan application of record. Cancelling or missing a callback later does not erase the home-value and urgency answers already stored next to a name — including when an adult child booked for a parent. 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. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

Eligibility-callback bookings and custom intake fields stored 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. Name, phone, homeowner age, home-value, remaining-equity, or health-driven urgency questions are fields you add; they are not documented defaults. Deed, ID, or appraisal uploads are files you accept; they are not documented defaults. One lead entry can store a parent's equity and urgency typed by an adult child who is not the homeowner. A submitted form is not a loan application of record. Notification emails and lead-buyer exports 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.

Form 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 visitor name, home value, or urgency note was sent. A page request from this script on a reverse-mortgage lead page is not proof anyone is out of money — and a pre-consent tag on that page can still treat reverse-mortgage-seeking intent as an audience segment from the URL alone. The page URL can say reverse mortgage even when no form is submitted. Consent timing has not been tested. Review which tags you enable on eligibility and callback pages.

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. Visitor names, phone numbers, homeowner age answers, home-value or remaining-equity fields, or health-driven urgency notes often depend on the fields you configure. An eligibility inquiry is not a loan application of record. A marketing-tag page request is not proof anyone is out of money. Cancelling or abandoning an inquiry later does not erase the equity and urgency answers already stored next to a name — including when an adult child filled the form and the homeowner never touched it. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the lead page, which lead buyers receive exports, and how long records and backups are kept. A "confidential consultation" 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 lending law, HECM regulation, give financial advice, or make elder-abuse-reporting claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on lead pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-reverse-mortgage-plugin-privacy