Medicaid planning plugin privacy
The worksheet that lists what the application will say you don't have
A Medicaid-planning site can look like a short intake and a file-upload box. The same form often asks for an asset inventory, a gift history, an income picture, and who is filling it out — and asks for bank statements and deeds — and stores those answers next to the family contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a spend-down worksheet next to a gift-history note, an income answer, a who-fills-it-out label, a statement upload, and a marketing pixel — the worksheet that lists what the application will say you don't have, typed once into a vendor table next to a newsletter signup. A spend-down worksheet row is a family-authored inventory, not a filed application. An uploaded statement or deed is a stored client document, not a verified asset. A who-fills-it-out answer is a configured label, not proof which relative typed the form. The elder named rarely touched the form. A page request is not proof any application was filed. The page URL can say medicaid-planning even when no form is submitted. Ask what happens to the asset inventory and gift-history rows after the family leaves — the quietest field is the gift history with its dates, a written timeline of transfers stored inside the window where two official stories can still be compared. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on the worksheet page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a Medicaid-eligibility-law or lookback-rule claim, a penalty-period claim, a fraud claim, an asset-protection-efficacy claim, a claim about any state program or planning firm, a claim about the planner's data-security practices, a provider-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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where spend-down worksheets, medicaid-planning intake, and page tags go
Worksheets and uploads on your WordPress site
Check which asset-inventory, gift-history, income, or who-fills-it-out fields you enable, who can open form entries and statement or deed uploads, which inboxes receive copies, and how long records, emails, and backups are kept after a family leaves — when the worksheet that lists what the application will say you don't have. Notification emails can also copy those fields off-site. One table can list every spend-down worksheet next to a deed upload and a gift-history answer. Ask your web vendor not to keep statement and deed uploads next to plaintext asset-inventory, gift-history, income, and who-fills-it-out rows in one open submissions list longer than operations need, and to purge worksheet rows when the planning relationship ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored worksheet is not a filed application. An asset inventory in a form table is not a verified statement of what the elder owns.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the medicaid-planning worksheet or intake page. That page request can reach a vendor host before anyone submits. The page URL can say medicaid-planning even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off spend-down worksheet and medicaid-planning intake pages if you do not want that page request. A browser scan cannot inspect stored entries or uploads. A "trusted planning partner" badge is not a verified storage path.
Spend-down worksheet, medicaid-planning 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 Medicaid-planning 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 |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which bank statements, brokerage statements, deeds, or other medicaid-planning documents you accept depends on the fields you add; they are not fixed medicaid-planning defaults. Filenames chosen by visitors can include account numbers or parcel IDs. An uploaded statement or deed is a stored client document, not a verified asset — and a mail copy of those files next to a spend-down worksheet is still a mailbox that holds the worksheet that lists what the application will say you don't have. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | 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. Asset-inventory, gift-history, income, or who-fills-it-out fields are fields you add; they are not documented defaults. Completing the form can store an asset inventory next to a gift-history note, an income answer, a who-fills-it-out label, and optional statement and deed uploads — typed once as the worksheet that lists what the application will say you don't have, into the same tables as a newsletter signup. A spend-down worksheet row is a family-authored inventory, not a filed application. An uploaded statement or deed is a stored client document, not a verified asset. A who-fills-it-out answer is a configured label, not proof which relative typed the form — and a staff login can open "Mom, house + checking + annuity, $40k gifted to kids 2022-2024, Social Security + pension, filled by daughter, statements.zip, deed.pdf" next to everyone else's newsletter signup. The elder named rarely touched the form. 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. | Spend-down worksheet stored in WordPress; optional statement and deed 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, OpenAI Pixel, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that an asset-inventory, gift-history, income, or who-fills-it-out field was sent. A page request from this script is not proof any Medicaid application was filed. The page URL can say medicaid-planning even when no form is submitted. Consent timing has not been tested. Review which tags you enable on spend-down worksheet and medicaid-planning 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. Asset-inventory, gift-history, income, or who-fills-it-out fields often depend on the fields you configure. A spend-down worksheet row is a family-authored inventory, not a filed application. An uploaded statement or deed is a stored client document, not a verified asset. A who-fills-it-out answer is a configured label, not proof which relative typed the form. The elder named rarely touched the form. A marketing-tag page request is not proof any application was filed. The page URL can say medicaid-planning even when no form is submitted. The worksheet that lists what the application will say you don't have — that is a storage path next to a gift-history field, not a feature these plugins claim. This page is about that medicaid-planning worksheet, not a bankruptcy-attorney disclosure, an assisted-living tour request, a home-care intake, a guardianship file, a reverse-mortgage application, an annuity-seminar registration, or an estate-sale inventory. Ask your web vendor who can open entries, whether a marketing tag loads on the worksheet page, and how long asset-inventory and gift-history rows and backups are kept after the family leaves. A "trusted planning partner" 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 Medicaid eligibility law, lookback rules, penalty periods, fraud, asset-protection efficacy, any state program, or any planning firm. Review stored records, uploads, connected services, exports, notification emails, marketing tags on worksheet 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-medicaid-planning-plugin-privacy